Skip to content

Conversation

@edgarfgp
Copy link
Contributor

@edgarfgp edgarfgp commented Oct 28, 2022

Attempt to Fix #14203

@edgarfgp edgarfgp marked this pull request as ready for review October 28, 2022 19:38
@edgarfgp edgarfgp requested a review from a team as a code owner October 28, 2022 19:38
@edgarfgp
Copy link
Contributor Author

Should this also behind a preview flag ?

@dsyme
Copy link
Contributor

dsyme commented Oct 29, 2022

I'm OK with considering this a bug fix,

@edgarfgp edgarfgp marked this pull request as draft October 31, 2022 10:14
…-not-using-the-obsolete-field

# Conflicts:
#	tests/FSharp.Compiler.ComponentTests/Language/ObsoleteAttributeCheckingTests.fs
@edgarfgp
Copy link
Contributor Author

edgarfgp commented Nov 14, 2022

@vzarytovskii I'm a little stuck here. Would appreciate some pointers or if you are willing to take this over will be also fine by me. I do not want to hold this from being fixed.

@T-Gro T-Gro self-assigned this Jan 12, 2023
| SynTupleTypeSegment.Slash _ :: SynTupleTypeSegment.Type ty :: args ->
let ms1, tpenv = TcMeasure cenv newOk checkConstraints occ env tpenv ty m
gather args tpenv (Measure.Prod(acc, Measure.Inv ms1))
| _ -> failwith "inpossible"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aw, I liked the "inpossible" more!

@T-Gro
Copy link
Member

T-Gro commented Feb 1, 2023

In the code added by this PR, BuildFieldMap tries to bring fields from inner expressions to the outer type in case of a double-nested record update.
I added a failing test, this is where is produces on the nested with clause.
It passes the field "ccont" to OuterType, which does not match.

image

@edgarfgp
Copy link
Contributor Author

Thanks @T-Gro for the pointers. I think I have a better fix in #15705. Closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Hide Obsolete warnings on record initializer not using the obsolete field

4 participants