[elm-discuss] Re: Multiple "Middleware" pattern instead of single *.program

On Thursday, November 2, 2017 at 12:56:52 PM UTC+1, Martin Janiczek wrote: > I have added a Navigation middleware example, see the updated demo: > https://janiczek.github.io/middleware/index.html > (Because *elm-lang/navigation* doesn't expose the *Location -> msg -> Sub &

[elm-discuss] Re: Multiple "Middleware" pattern instead of single *.program

On Thursday, November 2, 2017 at 10:30:10 AM UTC+1, Rupert Smith wrote: > > One problem I had was with TimeTravel.program which I was wrapping a > RouteUrl.navigationApp with. All the messages were then nested at the > time-travel level, and its UI did not support nested filtering, so I could

[elm-discuss] Multiple "Middleware" pattern instead of single *.program

Hello elm-discuss! I've been thinking about the **.program* pattern. Currently one has to choose one of the many different *.program functions and implement the rest of the functionality themselves, ie. they can't mix and match, say,

[elm-discuss] Re: Proposal: move Random.Extra.constant to Random

IIRC from conversations with Francesco, this thread started as a reaction to seeing that core's (to be 0.19) Random incorporated your Random.PCG's code but omitted `constant`. Can we know the reasoning behind the "it shouldn't be there" opinion? -- You received this message because you are

[elm-discuss] Re: Source Maps? /was Elm Dev Tools

I'm working on code coverage tool, although not in the "source maps + Istanbul" way: https://groups.google.com/forum/#!topic/elm-dev/1tHjTG1z6EM It currently lives on Github in Janiczek/elm-compiler .

[elm-discuss] Elm "missing library / I was blocked by ..." scoreboard?

Would it be a good idea to create Elm "scoreboard" at canny.io or something similar? (See https://react-native.canny.io/feature-requests for example) Seeing Twitter @elmlang mentions like: "It's sad that we lack touch subscription support on @elmlang", it seems to me that we could aggregate

Re: [elm-discuss] Re: No Runtime Exceptions - Still not computing

Dave, how do you think about JavaScript Promises? Where you code for the happy path (the chain of Promise.resolve().then().then().then()), any of which can throw, and have a .catch() handler that catches whatever the thrown value was and does something about it. The Elm Result type is very

[elm-discuss] Re: Possible compiler bug?

Sure, I just copied the function definition to my module that uses Random.Pcg instead of Random. There was no need to change the implementation, it just uses Random.Pcg.constant instead of Random.Extra.constant, I believe. import Random.Pcg as Random exposing (Generator) {-| Turn a list of

[elm-discuss] Re: Possible compiler bug?

) The compiler will then tell you that the imports are ambiguous. On Friday, August 19, 2016 at 11:29:00 AM UTC+2, John Bugner wrote: > > Why are duplicate imports allowed in the first place? > > On Friday, August 19, 2016 at 2:20:50 AM UTC-5, Martin Janiczek wrote: >> >>

Re: [elm-discuss] Possible compiler bug?

erator > > So when you call Random.together, you are passing it a > Random.Pcg.Generator, but it is expecting a core Generator. > > > On Fri, Aug 19, 2016 at 12:20 AM, Martin Janiczek <mar...@janiczek.cz > > wrote: > >> Hello, >> >> I've been stumped by

[elm-discuss] Possible compiler bug?

Hello, I've been stumped by a compiler error which I can't figure out. I think it's a compiler bug. (I'd like to maybe help fix that and contribute a PR - even though it might get incorporated into elm-compiler wy later or not at all, I could have my own elm-compiler and continue on the