# Any plans to ship \`OrderedTreeDictionary\` and \`OrderedTreeSet\`?

**URL:** <https://forums.swift.org/t/any-plans-to-ship-orderedtreedictionary-and-orderedtreeset/69365>\
**Category:** Collections\
**Created:** [January 10, 2024, 12:45am UTC](https://forums.swift.org/t/any-plans-to-ship-orderedtreedictionary-and-orderedtreeset/69365 "2024-01-10T00:45:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vanvoorden](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/vanvoorden/32/33619_2.png) [@vanvoorden](https://forums.swift.org/u/vanvoorden)\
**Post date:** [January 10, 2024, 12:45am UTC](https://forums.swift.org/t/any-plans-to-ship-orderedtreedictionary-and-orderedtreeset/69365/1 "2024-01-10T00:45:35Z")

</div>

[https://immutable-js.com/docs/v4.3.4/OrderedMap/](https://immutable-js.com/docs/v4.3.4/OrderedMap/)

Hi! Are there any plans for a future implementation of a `OrderedTreeDictionary`? I assume this would solve similar problems to the `OrderedMap` from Immutable JS… we could get the `O(log(n))` copy-on-write updates (similar to `TreeDictionary`) while also preserving the order items were added (similar to `OrderedDictionary`).

A (potential) `OrderedTreeSet` could also be part of that release.

I'm not really blocked on anything for now… but I could think of interesting things to do with that data structure if we decide to ship it! Thanks!
