fsharp / fsharp/fslang-suggestions

Infer latest matching record type for copy-and-update expressions

Open
#1,330 0 comments 8 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
373
Forks
21
PR merge metrics
No merged PRs in 30d

Description

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 `.`.

```f#
type Record1 = { X: int; Y: string }
type Record2 = { X: int }

// Successfully infers Record2
let getX a = a.X

// Fails with FS0667: Labels do not uniquely determine a corresponding record type.
// Ideally it should infer Record2.
let setX 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:
* [x] This is not a question (e.g. like one you might ask on [StackOverflow](http://stackoverflow.com)) and I have searched StackOverflow for discussions of this issue
* [x] 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](https://github.com/dotnet/fsharp)
* [x] 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
* [x] I have [searched both open and closed suggestions on this site](http://github.com/fsharp/fslang-suggestions/issues) and believe this is not a duplicate

Please tick all that apply:
* [x] 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 :+1: emoji on this issue. These counts are used to generally order the suggestions by engagement.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the issue's F# example and the stated comparison with `.` record-label inference. Review how the proposal would affect copy-and-update expressions when multiple record types match, and use the requested behavior and FS0667 example as the completion criteria; no implementation files or tests are identified in the payload.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.