Closed Lanayx closed 5 days ago
:white_check_mark: Found changes and release notes in following paths:
Change path Release notes path Description src/FSharp.Core
docs/release-notes/.FSharp.Core/8.0.400.md
Can somebody please help me pass unit tests? It fails with
Expected and actual surface area don't match. To see the delta, run:
Can somebody please help me pass unit tests? It fails with
Expected and actual surface area don't match. To see the delta, run:
I think you might want to run something like this
$env:TEST_UPDATE_BSL=1
>> dotnet test tests/FSharp.Core.UnitTests/FSharp.Core.UnitTests/ -c Release --filter "SurfaceArea"
That should update the baselines (sometimes you may need to run it twice), which you can then commit.
Can somebody please help me pass unit tests? It fails with
Expected and actual surface area don't match. To see the delta, run:
I think you might want to run something like this
$env:TEST_UPDATE_BSL >> dotnet test tests/FSharp.Core.UnitTests/FSharp.Core.UnitTests -c Release --filter "SurfaceArea"
That should update the baselines (sometimes you may need to run it twice), which you can then commit.
Thanks it worked, just as I figured out it should be $env:TEST_UPDATE_BSL=1
just as I figured out it should be $env:TEST_UPDATE_BSL=1
Ah, yeah, whoops
/azp run
@abelbraaksma you are welcome to review as well!
/azp run
Why would this functionality need to exist in the core runtime library? I would imagine that they could usefully exist in a nuget package and be downloaded only when someone actually had a need for them.
Whilst I am sure there are some apps that would benefit from access to this type of functionality, I don't expect it would be wouldn't be most or even many.
FSharp.Core is already much too big, and we ship two damned versions of it. And when it gets Crossgened or Ngened it gets huge, currently 5 MB.
We need to consider mechanisms to shrink FSharp.Core and only add to it, genuinely core functionality, that support core language features.
@smoothdeveloper posted this sugestion to the fslang suggestions thread:
https://github.com/fsharp/fslang-design/pull/732#issuecomment-2155552366
He also pointed out FSharpStats, which might be a good home for this type of functionality.
/azp run
/azp run
Alright, let's get this in. Thanks for your work @Lanayx. Let's spread the word :)
Description
FS-1135 implementation
Checklist
[x] Release notes entry updated: