In Elixir, the order of the keys is persisted if You have less than about 135 keys. I do not remember the exact number… nor where I learned that 
kokolegorille
0
Sebb
kokolegorille
Sebb
msimonborg
I only “learned” by playing around in the repl. High probability that I’m wrong
kokolegorille
I checked, as I do remember it was my first question on the Elixir forum.
32 is the number I had in mind at that time, I guess I inflated the number a little bit
No, it’s me
2
BartOtten
Final and conclusive solution; always deleting the 1st pair:
new_map =
%{“name” => “foo”, “address”=> “bar”}
|> Enum.into(%{}, fn
{“name”, v} -> {“1st”, v}
other -> other
end)
|> Map.drop([“1st”])
ps. try this at home but never at work.
2
BartOtten
At the moment of writing it’s true but one should not rely on it. So we may as well forget it as it’s an implementation detail that might change.
Still a fun Trivia fact to know though…for as long as it lasts
3
msimonborg
If it wasn’t piping a list into a Map function this would be the definitive way to drop the 1st pair of a map 
0
sabiwara
Elixir Core Team
If performance is a concern and we don’t want to create a full map from scratch, maybe we could do something like (disclaimer: I didn’t benchmark):
{first_key, _, _} = map |> :maps.iterator() |> :maps.next()
Map.delete(map, first_key)
(“first_key” in the sense of whatever keys comes out first 
)
1