You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to see better type inference for record copy-and-update expressions. When there are multiple matching record types in scope, it should default to the latest one, just like when using ..
typeRecord1={ X:int; Y:string }typeRecord2={ X:int }// Successfully infers Record2letgetX a = a.X
// Fails with FS0667: Labels do not uniquely determine a corresponding record type.// Ideally it should infer Record2.letsetX value a ={ a with X = value }
The existing way of approaching this problem in F# is using type annotations.
Pros and Cons
The advantages of making this adjustment to F# are: Improved usability and consistency.
The disadvantages of making this adjustment to F# are: Less explicit types (though again, it's consistent with . capabilities).
Extra information
Estimated cost (XS, S, M, L, XL, XXL): M
Related suggestions: (put links to related suggestions here)
Affidavit (please submit!)
Please tick these items by placing a cross in the box:
This is not a question (e.g. like one you might ask on StackOverflow) and I have searched StackOverflow for discussions of this issue
This is a language change and not purely a tooling change (e.g. compiler bug, editor support, warning/error messages, new warning, non-breaking optimisation) belonging to the compiler and tooling repository
This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it
This is not a breaking change to the F# language design
I or my company would be willing to help implement and/or test this
For Readers
If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.
The text was updated successfully, but these errors were encountered:
I'd like to see better type inference for record copy-and-update expressions. When there are multiple matching record types in scope, it should default to the latest one, just like when using
.
.The existing way of approaching this problem in F# is using type annotations.
Pros and Cons
The advantages of making this adjustment to F# are: Improved usability and consistency.
The disadvantages of making this adjustment to F# are: Less explicit types (though again, it's consistent with
.
capabilities).Extra information
Estimated cost (XS, S, M, L, XL, XXL): M
Related suggestions: (put links to related suggestions here)
Affidavit (please submit!)
Please tick these items by placing a cross in the box:
Please tick all that apply:
For Readers
If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.
The text was updated successfully, but these errors were encountered: