Ensure non-function types are not resolved as empty function declarations #753
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.
This fix still allows depending on attributes of a
Parameterized
that are themselvesParameterized
but are not declared as a parameter. Since some people are relying on this I did not want to remove that behavior. The actual bug that caused #635 was that if you depended on an attribute that was Parameterized it would treat it as if it was an undecorated method declaration, which are treated as if they depend on all parameters, i.e.:was functionality treated very similarly to this:
and since test does not declare dependencies that means
cb
will end up watchingname
andtest_param
.Fixes #635