FWIW I've already turned json-to-elm into kind-of-macros for my own
personal usage along with a couple of other things.
I don't think that elmx is a compelling use case though. I think it's
best to leave that stuff to the react people. Things like decoders,
encoders, reducing boilerplate,
Let me make the scenarios I mentioned more clear. I'm not advocating for a
macro language, I'm advocating for a means of doing code generation that is
consistent and maintainable. Producers could be solved with code
generation, elmx could be replaced with code generation (I don't think it
I also think that it should not be in the core. And I'd argue, that this
thread is about polling the community about the idea :)
I have a tiny beginning of an Elm parser written
using https://github.com/Bogdanp/elm-combine (awesome lib!!) that I could
push once it compiles (^^).
On Sunday,
