Gus
Gus
Implemented in #557
Implemented in #524 no breaking changes AFAIK. Also note about my comments above that at the moment struct tuples don't implement `ItemX` members.
We added docs in https://fsprojects.github.io/FSharpPlus/type-free.html with links to some excellent blogs, I recommend the first one, which has a very good explanation and uses F#+ Hopefully this close the issue...
Closing this: as: - `map >> map` reads good - we have the `Compose` type - we added applicative2 and applicative3 CEs - we deprecated `` which will allow us...
> * `map >> map` reads good Actually it doesn't read that good in pipe operations: `|> (map >> map) ...` I think using a combination of `|>>` and `map`...
Might be related to https://github.com/fsharp/fslang-suggestions/issues/905
As always with parsers there's the question of how smart my parser should be, where do you draw the line? Our current parsers uses `NumberStyles.Any` which makes them very flexible,...
OK, let's go with `parseStrict`, then the question remains for V2, I mean we can do breaking changes then but still which should be the default ? We have some...
I think a generic mechanism comes in handy when working with collections like a `NonEmptyList`.
I couldn't agree more. Here is the existing suggestion: https://github.com/fsharp/fslang-suggestions/issues/998