Myself and many other developers have been bitten by the fact that maps are sorted if they have less than 33 elements. Not because we believed that we should rely on the sort ordering of a map, but because we *accidentally* wrote an implementation that did, and didn't test it with more than 32 elements. Then at some point later in actual use things get strange, and debugging the above scenario can be very difficult (but is of course obvious in retrospect). This could be opt-in or opt-out, all the same to me, although unless the performance impacts are huge I think that it would save new developers even more time than experienced developers and so should potentially be opt-out. After a while when you start to see things "showing up in weird orders" you have an intuition to go look for a map being enumerated, but that isn't something a beginner would likely think of.
As far as I know this is an erlang thing, but I'm not too familiar with erlang and thought I'd float it by the elixir group first. I'm also not sure if its possible to change those constants based on Mix environments (or to change them at all), but I imagine that is where it will intersect with Elixir. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/a528c1bb-b8e1-429c-b1ff-a98db36ee2d6n%40googlegroups.com.
