fix: correct typos 'recieve' and 'occurence'

[thecaptain789]

Fixed typos in Python code: 'recieve' to 'receive' and 'occurence' to 'occurrence'.

[gemini-code-assist]

Summary of Changes

Hello @thecaptain789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the textual accuracy of the codebase by rectifying common spelling errors found in docstrings. These minor corrections contribute to improved readability and maintain the professional quality of the project's internal documentation.

Highlights

• Typo Correction: 'occurence': The spelling of 'occurence' has been corrected to 'occurrence' in the docstring for the structural_hash function within python/tvm/ir/base.py.
• Typo Correction: 'recieve': The spelling of 'recieve' has been corrected to 'receive' in the docstring for the call_packed_lowered function within python/tvm/tir/op.py.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• python/tvm/ir/base.py
  • Corrected 'occurence' to 'occurrence' in the docstring for structural_hash.
• python/tvm/tir/op.py
  • Corrected 'recieve' to 'receive' in the docstring for call_packed_lowered.

Activity

• No human activity has been recorded on this pull request since its creation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly fixes two typos. I've added one suggestion to fix another typo in the same area.

Additionally, while reviewing, I noticed a few other typos in the codebase that you might want to address in a follow-up PR, since they are outside the changed files:

• In python/tvm/ir/base.py:
  • line 191: assert_strucural_equal should be assert_structural_equal.
  • line 292: structrual_equal should be structural_equal.
• In include/tvm/node/structural_hash.h:
  • line 20: The comment says structural_equal.h but the filename is structural_hash.h.
• In tests/python/tir-base/test_tir_structural_equal_hash.py:
  • The word sequal is used multiple times (e.g., in get_sequal_mismatch). This appears to be a typo for s_equal or structural_equal.

[gemini-code-assist]

Since you're fixing a typo in this docstring, you could also fix another one on line 266: concistent should be consistent.

Suggested change

	first occurrence during the visit. The hash value of a graph node is
	combined from the hash values of its contents and the index.
	structural_hash is made to be concistent with structural_equal.
	first occurrence during the visit. The hash value of a graph node is
	combined from the hash values of its contents and the index.
	structural_hash is made to be consistent with structural_equal.

[tlopex]

@tvm-bot rerun

[tlopex]

@tvm-bot rerun

[cchung100m]

LGTM, thanks to @thecaptain789 😄