ordered icon indicating copy to clipboard operation
ordered copied to clipboard

Ordered sets and maps, implemented in pure clojure

Results 10 ordered issues
Sort by recently updated
recently updated
newest added

Since, as noted in the `ordered-set` docstring, `clojure.set/union` and other operations in `clojure.set` may reorder elements for efficiency, perhaps it would be useful for `ordered` to include (less efficient?) set...

OrderedMap doesn't implement `ITransientAssociative2` (which the `clojure.core` transient maps do), so using `contains?` or `find` on a transient OrderedMap throws a `contains? not supported on type: flatland.ordered.map.TransientOrderedMap` error.

Problem: When determining if a key exists in the backing map, we rely on matching the value against `:flatland.ordered.map/not-found`, which _probably_ won't be in backing map but could. By relying...

In order to keep things scoped, I'll close #43 and keep the rest of the work here

I've noticed that the library has a changelog, but it hasn't really been updated, which makes it pretty useless. It'd be nice if the recent changes were reflected in it.

There are test cases added that fail without these changes. (= ordered-map some-record-with-same-keys) returns true without these changes, for example, whereas Clojure's built-in maps are never = to any record,...

If a key is assoc'd multiple times to the same map, the first key, along with any metadata it might have, is the one that stays in the map. The...

I'd like to get a new release out but it seems the current CI setup suffers a bit from bitrot. Should we fix it or move over to Github actions...

See [#71](https://github.com/clj-commons/ordered/issues/71). `clojure.core/hash-unordered-coll` has been around since 1.6 and ordered only supports 1.8+ so there's no need to check for its existence anymore.

The `#ordered/map` data literal constructs an invalid data structure when read in the REPL, but not when used in a `def` form. ### Minimal repro at the REPL: ``` $...