delegation: fix ICE with double definition inside block in impl header#159140
Open
mansiverma897993 wants to merge 1 commit into
Open
delegation: fix ICE with double definition inside block in impl header#159140mansiverma897993 wants to merge 1 commit into
mansiverma897993 wants to merge 1 commit into
Conversation
When a function is defined inside a block (such as an anonymous constant or a macro like \core::direct_const_arg!\) in an impl header, its parent is the enclosing \Impl\ item. \n_kind\ determines if a function/delegation item is associated or free based on its parent's DefKind. When the parent is \DefKind::Impl\, \n_kind\ returned \FnKind::AssocInherentImpl\ or \FnKind::AssocTraitImpl\, even though the function is actually block-local (free). This incorrect classification propagates, hitting \unreachable!\ panics in delegation helper functions. Fix this by returning \FnKind::Free\ immediately if the function has \DefKind::Fn\ (since associated functions always have \DefKind::AssocFn\). Fixes rust-lang#159127
Collaborator
|
Thanks for the pull request, and welcome! The Rust Project is excited to review your changes, and you should hear from @jackh726 (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
Why was this reviewer chosen?The reviewer was selected based on:
|
Collaborator
|
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a function is defined inside a block (such as an anonymous constant or a macro like \core::direct_const_arg!) in an impl header, its parent is the enclosing \Impl\ item. \n_kind\ determines if a function/delegation item is associated or free based on its parent's DefKind. When the parent is \DefKind::Impl, \n_kind\ returned \FnKind::AssocInherentImpl\ or \FnKind::AssocTraitImpl, even though the function is actually block-local (free). This incorrect classification propagates, hitting \unreachable!\ panics in delegation helper functions.
Fix this by returning \FnKind::Free\ immediately if the function has \DefKind::Fn\ (since associated functions always have \DefKind::AssocFn).
Fixes #159127