It would not require a macro system. The compiler already generates co/decs for type aliases passed through ports. But this is specific to the port keyword and not available for other purposes like using the Http module.
On Friday, February 10, 2017 at 2:08:51 PM UTC-6, OvermindDL1 wrote: > > That is just because Rust has a fairly powerful (but incomplete) macro > system, that is not something that would really belong in Elm. ^.^ > > On Friday, February 10, 2017 at 11:19:49 AM UTC-7, Kasey Speakman wrote: >> >> Largest paint point for me in Elm is not mentioned: JSON. Rust appears to >> have adequate facilities for this (Serde). >> >> Otherwise, looks good. It was interesting to learn more about Rust and >> the intersection of features with Elm. >> >> On Wednesday, February 8, 2017 at 2:22:11 AM UTC-6, Martin Cerny wrote: >>> >>> (This is a cross-post from r/elm and r/rust) >>> >>> Hi all, >>> I wrote a blog post about the striking similarities between Elm and >>> Rust, and why I think it is no coincidence different languages took some >>> similar design paths. I'll be super happy to receive some feedback on the >>> post to let me improve it: >>> https://dev.to/martincerny/what-elm-and-rust-teach-us-about-the-future >>> >>> Thanks >>> Martin >>> >> -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
