Opened 11 years ago
Closed 2 years ago
#2275 closed enhancement (wontfix)
Move SCode.IMPORT
Reported by: | sjoelund.se | Owned by: | somebody |
---|---|---|---|
Priority: | high | Milestone: | 2.0.0 |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: | perost, adrpo |
Description
SCode.IMPORT is currently an SCode.Element with visibility information which is not needed. We could store the imports in a separate list (pretty-print always with imports at the top of the class) for efficiency.
Change History (9)
comment:1 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.3 to 1.9.4
comment:2 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.9.4 to 1.9.5
Milestone pushed to 1.9.5
comment:3 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.9.5 to 1.10.0
Milestone renamed
comment:4 Changed 7 years ago by sjoelund.se
- Milestone changed from 1.10.0 to 1.11.0
Ticket retargeted after milestone closed
comment:5 Changed 7 years ago by sjoelund.se
- Milestone changed from 1.11.0 to 1.12.0
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:6 follow-up: ↓ 7 Changed 6 years ago by casella
- Milestone changed from 1.12.0 to 2.0.0
@perost is this still relevant?
comment:7 in reply to: ↑ 6 Changed 6 years ago by perost
Replying to casella:
@perost is this still relevant?
You'll have to ask sjoelund.se about that. It's not very relevant to the new instantiation, although I guess it could be slightly more efficient.
comment:8 Changed 6 years ago by sjoelund.se
I am a little bit torn now. The bootstrapping does treat protected import differently from public import...
comment:9 Changed 2 years ago by perost
- Resolution set to wontfix
- Status changed from new to closed
Considering that we'd have to rewrite a lot of code to handle this and there aren't any clear need for it I don't see much point in keeping this ticket open.
Moved to new milestone 1.9.4