Perhaps. But as is the case with almost all of Elm, features are tested in
userland before they become considered for core. (specifically to find the
most rational API)
On Mon, Sep 26, 2016 at 11:34 AM suttlecommakevin <
suttlecommake...@gmail.com> wrote:
> If you read through that thread you
If you read through that thread you should be able to see what I mean.
IMO, if it was taken seriously, it would be supported as a first class
citizen.
On Monday, September 26, 2016 at 11:24:55 AM UTC-4, Scott Corgan wrote:
>
> What do you mean by "taken seriously"? (I'm curious).
>
>
I wish CSS was taken more seriously by Elm.
https://groups.google.com/forum/#!topic/elm-discuss/vvJGw1u7NVQ
On Sunday, September 25, 2016 at 6:50:07 PM UTC-4, Peter Damoc wrote:
>
> Regarding 1. I don't see how the compiler can deduce that a certain union
> type you used was suppose to have
Regarding 1. I don't see how the compiler can deduce that a certain union
type you used was suppose to have the meaning of ID and another meaning of
class
One way you can do this manually is to specialize the namespace manually
and then unpack it.
namespace : Namespace String Classes Ids msg
I built a small app using elm-css to spin the wheels. One of the things I'm
looking for is a "compiler's got my back" kind of experience with CSS;
however, I found a couple of oversights. I'm curious if there are some best
practices that might have given me a better experience:
1. I accidentally
