You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FuncItem steals the kinds and names from Argument on initialization, yet they are still accessed in several places - it's not clear who "owns" the information
arg.type_annotation is also not really used (the type is read from arg.variable.type) and is not even bound
In general, the relationship between Argument and Var (which is its first, well, argument) is not clear
More so, given that a single argument may be responsible for multiple variables in Python2.7. This is hacked away in the parser, but the way it is handled (making a regular argument and adding an unpacking statement) makes it very difficult to give precise error messages
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I have several comments/questions regarding
Argument
andVar
initialization_statement
is not needed. It is only being copied and printed. Without it, it becomes pure data. There's also redundant bookkeeping in other placesFuncItem
steals the kinds and names fromArgument
on initialization, yet they are still accessed in several places - it's not clear who "owns" the informationarg.type_annotation
is also not really used (the type is read fromarg.variable.type
) and is not even boundArgument
andVar
(which is its first, well, argument) is not clearThe text was updated successfully, but these errors were encountered: