Don Syme
Don Syme
Note to self: when creating first-class lambdas for .NET methods we aren't giving good names to implied arguments for the lambda. This can be improved: ```fsharp > System.IO.File.OpenText;; val it...
Is there a corresponding C# feature? (sorry - on mobile, haven't checked...) If so we should maintain alignment
@kkm000 Yes - For this sort of thing we're pretty much always happy to follow the C# approach to the same problem, as long as it is fully implemented and...
@kkm000 Great analysis thanks. > Can anyone familiar with the compiler (@dsyme is perhaps the ultimate authority) please give a ballpark estimate of the complexity involved in handling the above...
@ReedCopsey @TahaHachana - should we close this or fix it? Feels like we can live with this inconsistency?
A teams link will be posted here just prior to the call
Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_MTlmNzU5ZmUtZTAyYi00MTFjLWFhMmYtY2JlMjczNzM2ODMx%40thread.v2/0?context=%7b%22Tid%22%3a%2272f988bf-86f1-41af-91ab-2d7cd011db47%22%2c%22Oid%22%3a%22e374a10e-9340-46d0-a4be-5af5ac3602d5%22%7d
Yes, I agree. Marking as approved in principle
Some cases of this can I think be dealt with by changing this use of `UnifyRefTupleType` to `UnifyTupleTypeAndInferCharacteristics` in CheckExpressions.fs: | SynSimplePats.SimplePats (ps, m) -> let ptys = UnifyRefTupleType env.eContextInfo...
It seems like a plain bug