Skip to content

Conversation

@Numpsy
Copy link
Contributor

@Numpsy Numpsy commented Oct 19, 2025

Just having a go at building it with the RC .NET 10 version to see if it all works.

List.revIter (Binding >> add) bindings
// let! or use!
| SynExpr.LetOrUse(_, _, _, true, bindings, leftHandSide, _, _) ->
match bindings with
Copy link
Contributor Author

Choose a reason for hiding this comment

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

add <| Pattern rhs


// fsharplint:disable FL0025
Copy link
Contributor Author

Choose a reason for hiding this comment

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

temporarily turned this off as the self check was failing because this function is now 105 lines long and selfcheck wants if to be less than 100

@Numpsy Numpsy force-pushed the fcs10 branch 2 times, most recently from e5c21fc to 032f006 Compare November 3, 2025 22:10
@Numpsy Numpsy force-pushed the fcs10 branch 3 times, most recently from 6b9014d to 6ab840a Compare November 11, 2025 16:16
@Numpsy
Copy link
Contributor Author

Numpsy commented Nov 11, 2025

Not sure why the docs build failed with the build using the RTM FCS 43.10 when it worked with the RC2 version

@Numpsy
Copy link
Contributor Author

Numpsy commented Nov 11, 2025

Or is that just because the CI has started installing .NET 10 on it's own when it didn't this morning?

image

Apparently the use-dotnet action always installs the latest version now, which is .NET 10 as of earlier today - actions/setup-dotnet#674

@knocte
Copy link
Collaborator

knocte commented Nov 12, 2025

@Numpsy you're right, our daily CI run has started to fail today. Maybe setup-dotnet doesn't honor with: global-json-file: global.json properly anymore? We need to fix/workaround this in case that 674 issue is not fixed.

@knocte
Copy link
Collaborator

knocte commented Nov 12, 2025

@Numpsy actually, I don't think it's a bug in setup-dotnet action because all other CI jobs work except the docs one. So maybe it's a bug in Fornax? Fornax not honoring global.json?

@Numpsy
Copy link
Contributor Author

Numpsy commented Nov 12, 2025

It sounds like it's running with the .NET 9 SDK but trying to build as .NET 10 for some reason? (though the error shows the 9.0.306 SDK, and global.json is 9.0.201).
Not sure what's going on there at the moment, I didn't see that error when I built it locally (on Windows)

@Numpsy
Copy link
Contributor Author

Numpsy commented Nov 12, 2025

@Numpsy actually, I don't think it's a bug in setup-dotnet action because all other CI jobs work except the docs one. So maybe it's a bug in Fornax? Fornax not honoring global.json?

There does seem to be some machinery at https://github.com/ionide/Fornax/blob/master/src/Fornax/FSIRefs.fs for fishing for runtime libraries, so maybe you're right there and something is going wrong with .NET 10

@Numpsy
Copy link
Contributor Author

Numpsy commented Nov 12, 2025

I tried changing the CI to actually run as .NET 10 and that fails with a type check error in the build script - https://github.com/Numpsy/FSharpLint/actions/runs/19300021169/job/55193408198#step:7:12

Nothing can ever be simple :-(

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