Gus
Gus
I propose we add a mechanism (attribute or language construct) to consider the return type in overload resolution. The existing way of approaching this problem in F# is to add...
# Allow operators as active patterns I propose we allow to define operators as active patterns, so we'll be able to write code like this: ```fsharp match x with |...
It would be nice to allow other applications to create generic workflows. Currently a simple monad workflow is possible but in F# there are more operations available, some of them...
First redesign was a first step to get a more F#ish Numeric module. However many areas were not considered, specifically: 1a) Interaction with arbitrary .NET math operation like DateTime subtraction...
I would like to swap the type parameters order, so instead of `Validation` we define it like `Validation`. Also we could change the field names to `Okay` and `Errors`, the...
When converting from `Result` to `Validation` we need to either: - Make sure `'TError` is a Semigroup (this simply means that the type is additive) - Transform to a Semigroup...
Click “Files changed” → “⋯” → “View file” for the rendered RFC.
I propose we allow static members in interfaces. The CLR supports this, C# has this feature enabled since C# 8.0 and I see no reason why keep forbidding it in...
This will take advantage of static interfaces, which is the natural way of conding the `IEncoding` interface. The question is what do we do with codec for interfaces which uses...
We can add overloads for all numeric types supporting UoMs, they will have to be disambiguated from its non UoMized counterparts by using a different default level. This makes sense...