Re: [elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

Thanks, that helped me get everything working! I think this would be useful to add to the docs somewhere (either in elm-webpack-starter or in the elm tutorial itself, since it does mention webpack elsewhere). martin On Tue, Nov 8, 2016 at 3:54 AM, Wouter In t Velt wrote: > I use elm-webpack-sta

Re: [elm-discuss] port Maybe field behavior

Yes, indeed. Thanks for pointing me to that. On Thursday, November 10, 2016 at 11:13:08 PM UTC-6, Janis Voigtländer wrote: > > Isn't that exactly the following issue? > > https://github.com/elm-lang/core/issues/476 > > > Am 11.11.2016 um 04:41 schrieb Max Goldstein >: > > I also think this is re

[elm-discuss] Re: port Maybe field behavior

Op donderdag 10 november 2016 23:35:54 UTC+1 schreef Kasey Speakman: > > Anybody else run into this? > Yeah, I ran into this, but in a slightly different variant. My structure did not have the Maybe types. It was something like this: port newRecordForElm : (Record -> msg) -> Sub msg type alias

[elm-discuss] Re: Correct use of port subscriptions in a submodule reused multiple times?

Yeah, I too would recommend simplicity :) and one Ports.elm module at the top. My own productivity in Elm has improved enormously since moving to flat instead of nested, and moving away from components. Hope you will have the same experience going forward! -- You received this message because

[elm-discuss] Re: A spawned task cannot produce a result?

On Thursday, November 10, 2016 at 8:52:08 PM UTC, Max Goldstein wrote: > > So, I'm mostly speculating here, but could you use Task.andThen to get the > ID, which you then use to kill the task that updates the security token, if > necessary? Tried that, but the spawn task changes the return type

Re: [elm-discuss] Possible compiler bug while parsing type annotation in a let ?

Oh cool, thank you for the info, I will just comment it for now then. On Friday, November 11, 2016 at 5:09:31 PM UTC+8, Janis Voigtländer wrote: > > What you encountered is > https://github.com/elm-lang/elm-compiler/issues/1214, and it is fixed in > version 0.18 of the compiler. > -- You recei

Re: [elm-discuss] Possible compiler bug while parsing type annotation in a let ?

What you encountered is https://github.com/elm-lang/elm-compiler/issues/1214, and it is fixed in version 0.18 of the compiler. Am Freitag, 11. November 2016 schrieb Matthieu Pizenberg : > Hi, > > I just came accross one very strange compiler error and wanted to have the > point of view of the com

Re: [elm-discuss] Re: Is Elm really wrong?

On Thu, Nov 10, 2016 at 10:49 PM, Max Goldstein wrote: > What I meant was, Elm needs to choose differently from Haskell, at least > some of the time, or else there wouldn't be a reason for it to exist. It's the Object Oriented Programming. More precisely, the "fixed number of operations, unbou

[elm-discuss] Re: Gestures in Elm

Hi, m.hag... ;) Just to say that I am with you and would love to have support of these also. As maybe a small step I wrote recently a slightly more complete library handling also multitouch events, not only single touches.

[elm-discuss] Possible compiler bug while parsing type annotation in a let ?

Hi, I just came accross one very strange compiler error and wanted to have the point of view of the community before creating any github issue. I wrote some code to create tag more easily (seems to be trendy these days ^^) in a module Helpers.Views.elm. When I put a type annotation for a very