-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New copy-and-update warnings with Fable 4.4 #3567
Comments
@forki You are correct, sounds like a lot of people have concerns about warning 3560 and so it will be turned off by default in F# 8.0 final (post-RC2). It hasn't been merged in F# main yet, but I can cherry-pick it and have a new build shortly. |
Add |
@nojaf it's not just that particular one. there are more. But yes that is a valid workaround |
@ncave is |
I updated FCS in #3568 to turn off 3560 by default, it will be in the next release. |
I believe so, |
Friends, thank you very much for this super duper fast fix.
I'll test it tomorrow morning in the office.
Hugs.
Maxime Mangel ***@***.***> schrieb am Mi., 25. Okt. 2023,
19:48:
… Thank you @ncave <https://github.com/ncave>.
I just released a new version, @forki <https://github.com/forki> can you
please check if this fixed all the warnings you had?
—
Reply to this email directly, view it on GitHub
<#3567 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOANAPIVNG5DQ2GM7O4QLYBFGFNAVCNFSM6AAAAAA6PKRLICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZZG43DMNJZHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
yes it works. Thank's a lot. |
It looks like Fable 4.4 is using F# 8 features and also emits F# 8 warnings:
We see LOTS of new warnings. Things like:
warning FSHARP: This copy-and-update record expression changes all fields of record type 'MyRecordType'. Consider using the record construction syntax instead. (code 3560)
@MangelMaxime @ncave Is this expected?
references dotnet/fsharp#16182
The text was updated successfully, but these errors were encountered: