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

FSharpx.Extras v3.2.0 breaks compilation #436

Closed
Micha-kun opened this issue Jul 17, 2024 · 7 comments · Fixed by #437
Closed

FSharpx.Extras v3.2.0 breaks compilation #436

Micha-kun opened this issue Jul 17, 2024 · 7 comments · Fixed by #437

Comments

@Micha-kun
Copy link
Contributor

Description

FSharpx.Extras v3.2.0 has a forced restriction that Fsharp.Core requires to be (>= 6.0.6 && < 6.1.0), making projects using other versions to break. v3.1.0 didn't have that restriction (>= 4.6.2).

Repro steps

Create an F# project with .Net 8 and try to add FSharpx.Extras v3.2.0 nuget

Expected behavior

Project with FSharpx.Extras compiles correctly

Actual behavior

Project with FSharpx.Extras fails to compile

Known workarounds

Install FSharpx.Extras v3.1.0 or force Fsharp.Core to be (>= 6.0.6 && < 6.1.0)

Related information

  • Operating system: Windows 11
  • .NET Runtime, CoreCLR or Mono Version: .Net 8.0
@gdziadkiewicz
Copy link
Collaborator

Hi @Micha-kun I will fix that tomorrow

@Micha-kun
Copy link
Contributor Author

Thanks 👍

@OkkeHendriks
Copy link

Having the same problem

@gdziadkiewicz
Copy link
Collaborator

Hi, I just published a new version (3.2.1) with the requirement on FSharp.Core relaxed. Can you confirm if it works for you as expected?

@bert2
Copy link

bert2 commented Jul 28, 2024

Thanks for the fix! I don't see anymore compiler errors here :)

@Micha-kun
Copy link
Contributor Author

Hi, I just published a new version (3.2.1) with the requirement on FSharp.Core relaxed. Can you confirm if it works for you as expected?

Yep! It's working now :) Thank you!

@OkkeHendriks
Copy link

Yes, checked again with 3.2.0 -> compile warning; at 3.2.1 it is fixed! Thanks.

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 a pull request may close this issue.

4 participants