Skip to content
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

Upgrade FSharp.Compiler.Service to v43.8.200 to remove workaround in NoPartialFunctions rule #698

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

webwarrior-ws
Copy link
Contributor

NoPartialFunctions needed a workaround because of a bug in FSharp.Compiler.Service library.
In FSharp.Compiler.Service to v43.8.200 that has bug has been fixed.

This PR upgrades FCS to v43.8.200 and makes necessary changes to code. Workaround is removed.
Packages FSharp.Core and Ionide.ProjInfo.* also had to be upgraded to latest stable versions.

@knocte knocte changed the title Upgrade FSharp.Compiler.Service to v43.8.200 and remove workaround in NoPartialFunctions rule Upgrade FSharp.Compiler.Service to v43.8.200 to remove workaround in NoPartialFunctions rule Feb 15, 2024
@webwarrior-ws webwarrior-ws force-pushed the remove-nopartialfuncs-workaround-squashed branch from a1ff3e7 to db33ff6 Compare February 15, 2024 09:34
@knocte
Copy link
Collaborator

knocte commented Mar 4, 2024

Even though this doesn't have conflicts, I'd prefer to get a rebase before merging, just to be on the safe side.

Upgrade FCS to the latest stable version (43.8.200).
Adapte code to changes in FSharp.Compiler.Service.
@webwarrior-ws webwarrior-ws force-pushed the remove-nopartialfuncs-workaround-squashed branch from c9f3bd8 to ee4ecfb Compare March 4, 2024 12:11
@webwarrior-ws webwarrior-ws reopened this Mar 4, 2024
@webwarrior-ws
Copy link
Contributor Author

Even though this doesn't have conflicts, I'd prefer to get a rebase before merging, just to be on the safe side.

Rebased.

@knocte
Copy link
Collaborator

knocte commented Mar 4, 2024

Can you move the commit NoPartialFunctions: remove workaround to be the last one please?

Fix errors in CyclomaticComplexity tests cause by incorrect
indentation of generated code.
Fix bug in tests where empty sets of different types would be
treated as different.

Error was:
```
Expected is <Microsoft.FSharp.Collections.FSharpSet`1[System.IComparable]>, actual is <Microsoft.FSharp.Collections.FSharpSet`1[System.String]>
```
Upgrade Ionide.ProjInfo.* packages to latest stable (0.63.0)
because current version causes bug when running self-check:

```
Lint failed while analysing /home/runner/work/FSharpLint/FSharpLint/FSharpLint.sln.
Failed with: Method not found: 'FSharp.Compiler.CodeAnalysis.FSharpReferencedProject FSharp.Compiler.CodeAnalysis.FSharpReferencedProject.CreateFSharp(System.String, FSharp.Compiler.CodeAnalysis.FSharpProjectOptions)'.
Stack trace:    at [email protected](ProjectOptions p)
...
```
Remove workaround introduced in [1] for bug in FCS [2] that was
fixed in FCS 43.8.200.

[1] 106be3f
[2] dotnet/fsharp#16121
@webwarrior-ws webwarrior-ws force-pushed the remove-nopartialfuncs-workaround-squashed branch from 86442cb to 9e5f360 Compare March 5, 2024 09:15
@webwarrior-ws
Copy link
Contributor Author

Can you move the commit NoPartialFunctions: remove workaround to be the last one please?

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants