I assume this part isn’t directed at me?
For the record I’m personally opposed to this making it into the language and think it’s better it exists in libraries. I just wanted to share that thread as it has the most discussion and, in spite of my feelings, your proposal was an epic-good read and lesson in proposal writing. I still think back to it when I try and outline tech concepts in writing 
I’d really like to have that feature.
Did you think about adding sth to convert between normal and es6-maps-codebases.
Would be easier to use in teams.
I’d personally be very happy with a solution like that built into the language.
Assuming you’re talking about es6_maps:
The pin operator support is something I’d like to see in the library in the future – the bigest impediment being that %{^x, y: 1} is not valid syntax and doesn’t make it to the AST stage, unlike %{x, y: 1}.
Map & struct updates are supported and there’s a couple examples in the README.
From my PoV the problem is, it’s really tricky to implement this as a library in a way that feels like a natural part of the language.
I was fine with requiring use Es6Maps in each module that wanted shorthands, but between @on_definition deliberately not calling macros, @before_compile actually happening after a compilation pass, and this post from @josevalim, there weren’t many options left aside from modifying the compiler in-flight to get this. It would be great to be able to create language extension PoCs that could make it into the standard implementation.
Already added, there’s an Es6Maps.Formatter included in the library. You add it as plugins: [Es6Maps.Formatter] to .formatters.exs, call mix format, and all of your maps will be converted.
Unless you mean something like “display shorthand maps in the editor, save normal maps to disk”? That sounds like an interesting feature for ElixirLS.
Sis not know this lib so far. Just skimmed the thread.
Thinking out loud: having ‘—revert’ as formatter would enable auto-expansion while writing the code (format-on-save)? If so the writing becomes easier while its still k/v in the code base.
Yep, technically you can skip adding :es6_maps to compilers, and add this to .formatter.exs to get that
# .formatter.exs
[
plugins: [Es6Maps.Formatter],
inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"],
es6_maps: [map_style: :vanilla]
]
I have released the v1.0.0 version of es6_maps!
The major changes are:
es6_maps now amends the Elixir compiler at a different point (:elixir.string_to_tokens/5), which improves compatibility with other Elixir tools and happens to be a more stable API.The v1.0.0 is also meant to signal production readiness. The library has been battle tested over the past year, and with the changes above I’m confident of its stability going forward.
GitHub: GitHub - kzemek/es6_maps: `%{foo, bar: 1}` — ES6-like shorthand syntax for Elixir maps and structs · GitHub
Hex: es6_maps | Hex
HexDocs: es6_maps v1.0.3 — Documentation