Skip to content

Remove deoptimizations in FSharp.Test.Utilities #18606

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

Merged
merged 1 commit into from
May 26, 2025

Conversation

majocha
Copy link
Contributor

@majocha majocha commented May 24, 2025

Just to see if things still work. I can't think of a reason this particular project needs to disable optimizations and tailcalls.

Copy link
Contributor

✅ No release notes required

@github-project-automation github-project-automation bot moved this from New to In Progress in F# Compiler and Tooling May 26, 2025
@T-Gro
Copy link
Member

T-Gro commented May 26, 2025

If this does not touch baselines, it is good to go for me.

One reason I could in theory imagine is stability across DEBUG vs RELEASE baselines, to make dev life easier (since typically one would run tests in debug from IDE, whereas CI is running everything in release).
This might have been historical when tests were executed in a different way or the config from test hosting project to actual tests was just inherited.

@T-Gro T-Gro merged commit 644dc23 into dotnet:main May 26, 2025
39 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in F# Compiler and Tooling May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants