BenchmarkDotnet config option - ignore that Test.Utilities is not optimized #15038
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses #14913
"Assembly FSharp.Compiler.Benchmarks which defines benchmarks references non-optimized FSharp.Test.Utilities".
Test.Utilities is used for the ProjectWorkflowBuilder, which is not what we are benchmarking - it is just sugar to describe scenarios.
We want to keep it unoptimized for easier debugging of tests, which also make use of it.