Yes, precedence things usually does this but decoders are trickier because
you can extract the exact same information from multiple shapes of data.
You can have both
[ {"children": {"data" : "somedata"}}, {"children": {"data" :
"someOtherData"}}, ...]
and
{"children": [{"data": "somedata"}, {"data": "someOtherData"}, .. ] }
On Sun, Sep 4, 2016 at 8:52 PM, Charlie Koster <[email protected]> wrote:
> Oh sweet. I guess that makes sense since := is an infix function.
>
> I guess I'm surprised that the compiler didn't say anything. Precedence
> issues usually end up sending the wrong things to functions in my
> experience.
>
> Anyway, I appreciate the help!
>
> --
> 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.
>
--
There is NO FATE, we are the creators.
blog: http://damoc.ro/
--
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.
