-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix IR for top level functions with using-for #2367
Conversation
Important Auto Review SkippedAuto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
@property | ||
def using_for_complete(self) -> Dict[USING_FOR_KEY, USING_FOR_ITEM]: | ||
""" | ||
Dict[Union[str, Type], List[Type]]: Dict of top level directive |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This type doesn't match in the comment and the return signature is different than the definition. If we return an empty dict and not None
, it isn't Optional
Can we add the PR example as a regression test please? |
Previously when an item in a top level function with using-for the IR was an
HIGH_LEVEL_CALL
instead ofINTERNAL_CALL
/LIBRARY_CALL
. This was happening because in the conversion we only looked at the using-for forFunctionContract
.Before
After