Kasey Speakman

Ran into this today with a barcode scanner and an input field. Scanner typed faster than Elm's update/render cycle. This caused characters to get dropped in the input field. It's...

Here's what Elm-style looks like, same for records (curly brace instead of paren). I've had a few cases where this made sense, usually method/constructor calls where I include parameter names...

Adding an alternative. We'll use static data, then it typically gets moved to a DB after a few updates. I use this approach which works for both. ```fsharp type Item...

I've used both ways now in Elm (annotations above) and F# (annotations inline). At first, I loved Elm annotations and wished F# had them. But as time went on the...

VS2019 comes with (experimental) CodeLens feature, which will display an annotation above (or beside) the function. With this, most of the reason I liked type signatures from Elm are satisfied:...

> I wish F# emitted a warning for a top level function without an annotation. If you really wish it, make an issue suggesting the feature (maybe in the compiler...

@yatli @Happypig375 Example syntax if extrapolated for consistency: ```fsharp open System // typed: & | type MyRecord = Id: Guid & Name: string type MyDU = Id: Guid | Name:...

@voronoipotato Thanks for this adding this perspective to my life! Makes me feel less weird about using extra let statements to avoid nested parens. (More understandable to me.) Also gives...

Oh I use unparen tuples constantly. Can't use em in fn arguments though. I avoid semicolons whenever feasible by using newlines. Frequently get caught typing commas like nature intended 🤣...

> you can use ||> for lambdas :) . I'm trying to imagine that usage. Further reflection, I see advantages to the `;`. (Not that it had any chance of...