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
Currently the metaclass node is assumed to be a string. This is inconsistent, requires workarounds such as passing '<error>' from the parser to the semantic analysis phase, and makes it awkward to handle metaclasses that come from different contexts (as in python2).
Making it an Expression works cleanly as far as I can tell, and reduces code duplication.
The text was updated successfully, but these errors were encountered:
Currently the metaclass node is assumed to be a string. This is inconsistent, requires workarounds such as passing
'<error>'
from the parser to the semantic analysis phase, and makes it awkward to handle metaclasses that come from different contexts (as in python2).Making it an Expression works cleanly as far as I can tell, and reduces code duplication.
The text was updated successfully, but these errors were encountered: