Re: [elm-discuss] Equality Error Undecidable

> On Jul 11, 2016, at 7:28 PM, Mark Hamburg wrote: > > On Jul 11, 2016, at 4:23 PM, Mark Hamburg wrote: >> >> A bigger problem is that the requirement that something be equatable or the >> property that a type is not equatable becomes a hidden

Re: [elm-discuss] What is the purpose of this board?

Please do not make a new thread to list them all. Most of them are likely to have been brought up before. The most useful place for quality issues to be brought up is in the Github issue tracker for the relevant project (in the example you mention above, check the elm compiler project

Re: [elm-discuss] What is the purpose of this board?

> > If you have taken the time to learn Elm to a level where you start to > understand its core values > I think I'm already at that point. I like that Elm values simplicity and clarity, even if it means bucking the current convention. For example, I think switching from the Haskellian

Re: [elm-discuss] handling URL params in ELM

Have you seen the examples for elm-lang/navigation? https://github.com/elm-lang/navigation/blob/master/examples/Counter.elm I think it is easy to adapt this one for your needs. If you want something more sophisticated you could use evancz/url-parser On Mon, Jul 11, 2016 at 9:37 PM, William

[elm-discuss] Czaplicki on Elixir Fountain

Great interview https://soundcloud.com/elixirfountain/elixir-fountain-evan-czaplicki-2016-07-11 -- 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

[elm-discuss] handling URL params in ELM

I have a feeling this is a really stupid question but here goes. So I have this Elm card game app: deepfinesse.com/demo.html I'd like the card layout that shows up which is presently hardcoded in the Elm source to come from a URL param, ala: deepfinesse.com/demo.html?deal=AJ743.KQ2.7.984

Re: [elm-discuss] Equality Error Undecidable

There have been many discussions on Github about improving the function equality situation. To quote Janis's comment here : > This has often been discussed. In GitHub issues like here >

Re: [elm-discuss] Task.onError with 'always' is a bit error prone - an argument for lambdas?

All the more evidence that this is tricky! I used to really like always, but I'm starting to rethink that. On the new elm-test (not yet released), we have to use lambadas because always eagerly evaluates its argument. -- You received this message because you are subscribed to the Google

Re: [elm-discuss] Equality Error Undecidable

In my animation library, I define an 'equal' function because animations include a function. I sample the function maybe 5 times for each animation; it's rare to get a false positive. It's possible that the "marketing" needs to be clarified, but it will always be possible to get a runtime

Re: [elm-discuss] Task.onError with 'always' is a bit error prone - an argument for lambdas?

oops, sorry for the premature send! what I was saying is, the argument that gets passed is not an error. But that's ok, since the argument gets thrown out, you could also just write (\_ -> (Task.succeed "fallback value")) But I agree, using "always" is a very special case. Even though it has

Re: [elm-discuss] Task.onError with 'always' is a bit error prone - an argument for lambdas?

One correction: the argument that gets passed to (\error -> (Task.succeed "fallback value")) On Mon, Jul 11, 2016 at 12:03 AM, Ian Mackenzie wrote: > So I was playing around in the Elm REPL with various Task functions and > stumbled onto the following: > >

[elm-discuss] Re: Stuck on custom event handlers and JSON decoder for select element

I found a good solution for my issue. Still need to dig into what's going on here. I find this idea of Json decoding in Elm is still a bit of a struggle for me. Here is what got things working for me: http://stackoverflow.com/questions/37376509/work-with-elm-and-select On Friday, July 8, 2016

Re: [elm-discuss] What is the purpose of this board?

This is the general discussion forum for Elm. Almost anything related to Elm is welcomed here. :) Some of the questions/issues one has might find a better fit on the Slack channel Some of the issues might be more appropriate to be discussed in elm-dev. If you have found a bug and were able to