Ticket #2431 (closed tweak: obsolete)
immutable collections -- iterator
Reported by: | stefan | Owned by: | stefan |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | uncategorized | Version: | 2.0 |
Keywords: | Cc: | ||
Category: | unknown | Effort: | |
Importance: | Ticket_group: | immutable collections | |
Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
Billable?: | yes | Total Hours: | 0 |
Analysis_owners: | stefan | Design_owners: | stefan |
Imp._owners: | Test_owners: | ||
Analysis_reviewers: | pap | Changelog: | Changelog |
Design_reviewers: | Imp._reviewers: | ||
Test_reviewers: | Analysis_score: | 3 | |
Design_score: | 0 | Imp._score: | 0 |
Test_score: | 0 |
Description (last modified by stefan) (diff)
Research performance of ImmCollection iterator's performance and where possible, improve it.
wiki page: IMM_COLLECTIONS_REFACTOR
Change History
comment:1 Changed 15 years ago by stefan
- Owner set to stefan
- Status changed from new to s1a_analysis_started
comment:2 Changed 15 years ago by stefan
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:5 Changed 15 years ago by pap
- Status changed from s1b_analysis_finished to s1c_analysis_ok
- Analysis_reviewers set to pap
- Analysis_score changed from 0 to 3
- Passes but is too simple.
- Aren't iterators and foreach the same thing?
- The design should contain those places with performance problems even the ones that cannot be improved.
Note: See
TracTickets for help on using
tickets.