New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
constraints and local opens as proper nodes vs extra field #7129
Comments
Comment author: @trefis Jacques said:
Alain said:
Personally I tend do agree with Alain on that one. |
Comment author: @garrigue No bug here. |
FTR local opens in expressions are now actual an actual node, not stored in the extra field. Nothing happened on the side of type constraints. |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
This is a bit of a meta-issue on code-cleanliness. I also agree with @alainfrisch and @trefis that making parsetree and typedtree completely mirrored, without any extra nodes, would be nice. It's just a matter of someone doing it. |
Original bug ID: 7129
Reporter: @trefis
Status: acknowledged (set by @damiendoligez on 2016-02-08T11:28:43Z)
Resolution: open
Priority: low
Severity: feature
Target version: undecided
Category: typing
Bug description
Context: #441
The code submitted in #441 is a quick hack which should be removed after 4.03's release.
This issue is here to keep track of that, as well as discuss the potential long term solutions.
The text was updated successfully, but these errors were encountered: