Don Syme
Don Syme
Yes, we can generate `$`, `init`, `reqd`, I don't see why not.
The original suggestion looks entirely reasonable, I'll mark it as approved. I agree with omitting Result.get. We can consider Option.get in a separate suggestion > Also, do we want a...
I guess we would support this if it's a .NET standard. You're right that they are potentially of use to source analysis tools.
@Smaug123 @cartermp I'd be happy with the addition of an off-by-default compiler warning.
@robkuz Would the defaults flow through inference, so let f (a,b,c,d) = { foo=a; bar=b; baz=c; foobar=d } somehow gets default inference behaviour?
I actually really like this suggestion in principle. It could fit very nicely with F# inference, and those are the sort of features I tend to like. However three upvotes...
One problem with the above is that in the case of a multi-argument delegate there's no simple way to *always* get a direct delegate Consider this code: ```fsharp type C()...
I'll mark this as approved in principle, though there is one technical question remaining as mentioned above.
As an aside, it should be noted that delegate construction always delays (and reevaluates) the relevant function on each call, so, for example ```fsharp new System.Action(failwith "") ``` is equivalent...
Notes on the testing matrix for this * "unit returning" cases should be considered. This is the matrix of cases where the compiled representation of the target method returns `void`...