Phillip Carter
Phillip Carter
> The disadvantages of making this adjustment to F# are .. ? dont know if there is any One I can immediately think of is that F# supports shadowing and...
Agreed, this feels like something that's just the right thing to do. I have approved this in principle. While I cannot speak for the priority of the team to implement,...
I see this primarily as a compiler bug, since we _should_ be able to disambiguate between a type definition and an operator usage, but I'm not sure how feasible that...
RFC is written.
@davidfowl > The other is around supporting conversion from F# lambdas to Delegate without an explicit cast. F# supports direct conversions at the call site like so: ```fsharp open System...
If https://github.com/fsharp/fslang-suggestions/issues/765 were allowed, then this would naturally fall out of it from a compiler analysis standpoint. It was my main motivation for filing that suggestion.
Just to comment on this with a real-world case - I took a little dive into what it would look like to "spannify" some of the internals of the compiler....
@mciccottidmg That is actually by design and not related to this suggestion. Partial application implies boxing, which contradicts the rules for byrefs.
Related: https://github.com/fsharp/fslang-suggestions/issues/1074 and https://github.com/fsharp/fslang-suggestions/issues/907 @dsyme @KathleenDollard I think we should consider all three of these (even if they just get done piecemeal)
This is related to several other quirks, often when mixing unions and modules with the same name. Definitely in favor of this.