Op maandag 6 juli 2015 10:42:43 UTC+2 schreef dmic...@gmail.com:
The semantics of a set doesn't guarantee an order either (even though it's
implementation might), I'd sort over the keys and use the resulting
collection as hash-map key so you are independent of any clojure-intrinsic
The semantics of a set doesn't guarantee an order either (even though it's
implementation might), I'd sort over the keys and use the resulting
collection as hash-map key so you are independent of any clojure-intrinsic
behavior.
On Thursday, July 2, 2015 at 3:06:00 AM UTC+2, Fluid Dynamics
But with a set, the ordering doesn't matter, since #{:foo :bar} = #{:bar
:foo}, so a set as a dispatch value should work just fine.
On Mon, Jul 6, 2015 at 1:45 AM, dmichu...@gmail.com wrote:
The semantics of a set doesn't guarantee an order either (even though it's
implementation might), I'd
That was exactly what i'm doing to fix it. I didnt care about the actual
order but assumed the order was going to stay the same. Bad assumption.
Thank you all for the feedback.
Op donderdag 2 juli 2015 03:06:00 UTC+2 schreef Fluid Dynamics:
On Wednesday, July 1, 2015 at 3:54:03 PM UTC-4, Jo
Hey,
I when i tried to run my program with the shiny new 1.7, it broke. I have
traced it down to the fact that zipmap (
https://github.com/clojure/clojure/blame/master/src/clj/clojure/core.clj#L2940)
does returns the keys in a different order than i'm used to.
e.g clojure 1.6:
nREPL server
Unsorted hash maps changed their seq order from Clojure 1.5.1 to Clojure
1.6.0, and some unsorted maps changed their seq order from Clojure 1.6.0 to
Clojure 1.7.0. If you are relying on the seq order of unsorted maps, your
program is at risk of breaking across Clojure versions.
Andy
On Wed, Jul
On Wednesday, July 1, 2015 at 3:54:03 PM UTC-4, Jo Geraerts wrote:
Hey,
I when i tried to run my program with the shiny new 1.7, it broke. I have
traced it down to the fact that zipmap (
https://github.com/clojure/clojure/blame/master/src/clj/clojure/core.clj#L2940)
does returns the
