Thanks to everyone who pointed out that the compiler was catching my mistake in using the wrong `>` inside of a definition of `>`.
Related to: > > Also: I’m finding these types fairly awkward to work with, in that I have > functions that want to operate on the base type and also the wrapping type > (typically to pass work to other functions). It seems to me that means I have > to do things like this semi-contrived example: > > animationSteps dropsPerSecond = > let > (DropsPerSecond raw) = dropsPerSecond > in > if raw > 8.0 then > steadyStream > else > fallingDrop dropsPerSecond … someone pointed out to me on twitter that `as` works in function heads: `animation ((DropsPerSecond raw) as dropsPerSecond) = …` Note that the parentheses are required. I haven’t been able to find a description of `as` in the documentation. If it’s not explained, I’ll make a todo item to submit a writeup. -- 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.
