Skip to content

Conversation

@weswigham
Copy link
Member

Fixes #25672

A type parameter merged with a parameter has both type and value meanings, and both the Type and the Value masks contain some of the same meanings (Class, Enum, EnumMember and Assignment), so comparing a target meaning (and not a flags member) against just one of them almost always yields true. We really only want to limit the scope of the parameter meanings of the symbol to the function body, so we need to ensure that the meaning we're looking for is really just the value meanings we actually care about (in this case, FunctionScopedVariable).

@weswigham weswigham changed the title Exclude the overlap between Type and Value when checking for parameter visibility Fix checking for type parameter visibility when merged with a parameter Sep 28, 2018
@weswigham weswigham merged commit 1e55d65 into microsoft:master Oct 2, 2018
@weswigham weswigham deleted the type-parameters-and-parameters branch October 2, 2018 16:41
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants