OrderMap 1.0 Roadmap

[bluss]

Must have

• Full consistency check list should be complete and remaining discrepancies should be fixable backwards compatibly or marked as not important (Full Consistency With HashMap #19)
• Mutable keys Move mutable key access to a trait #7 Add trait MutableKeys #39
• Settle crate name Change name? #14 Settle removal semantics Add ordered_remove with O(n) perf. #15 (and split crate for full insertion order Added Tombstones #12)
• Move map stuff to map:: submodule (like set::) Move OrderMap into the map submodule #60

Nice to have

(can be added backwards compatibly)

• Full consistency (Full Consistency With HashMap #19). Being drop in is good, but some of the details don't matter much, you can be effectively drop in without being 100% type by type compatible.
• OrderSet Feature Request: OrderSet? #8
• Order preserving retain Make .retain() in-order and preserve-order #56
• Every public item has documentation

At Release

• Blog post about the name change and explain the properties of the data structure

[bluss]

Next version will be the last with the ordermap name. Then we make one with the same version and compatible API under the new name (IndexMap as of this writing).

[bluss]

Crate name question is decided, IndexMap from #14