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

Stabilize new lazy vals #16614

Merged
merged 6 commits into from
Jan 9, 2023
Merged

Conversation

szymon-rd
Copy link
Contributor

Resolve #16555

@szymon-rd szymon-rd requested a review from prolativ January 4, 2023 12:40
@szymon-rd szymon-rd added this to the 3.3.0-RC1 milestone Jan 4, 2023
@@ -45,7 +45,7 @@ class CompilationTests {
compileFilesInDir("tests/pos-custom-args/erased", defaultOptions.and("-language:experimental.erasedDefinitions")),
compileFilesInDir("tests/pos", defaultOptions.and("-Ysafe-init")),
// Run tests for experimental lightweight lazy vals
compileFilesInDir("tests/pos", defaultOptions.and("-Ysafe-init", "-Ylightweight-lazy-vals", "-Ycheck-constraint-deps"), FileFilter.include(TestSources.posLazyValsAllowlist)),
compileFilesInDir("tests/pos", defaultOptions.and("-Ysafe-init", "-Ylegacy-lazy-vals", "-Ycheck-constraint-deps"), FileFilter.include(TestSources.posLazyValsAllowlist)),
Copy link
Contributor

Choose a reason for hiding this comment

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

Update the comment above.
Also would we now want to run all the pos and run tests instead of just the ones from the lists?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think that no, we still want to run these tests, but now for legacy instead of the new lazy vals. New lazy vals will be now tested in standard pos and run tests. But the comment should be updated ofc.

object Evaluating extends LazyValControlState

/**
Copy link
Contributor

Choose a reason for hiding this comment

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

Wasn't the comment supposed to stay?

@@ -0,0 +1 @@
-Ylegacy-lazy-vals
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we really need that? I thought .flag files in tests are deprecated and vulpix doesn't even take them into consideration

Copy link
Contributor Author

@szymon-rd szymon-rd Jan 5, 2023

Choose a reason for hiding this comment

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

It does work, the generated code differs. Mainly because the previous PR on lazy vals implemented .flag files for printing tests 😄 Is it the direction we are taking - to deprecate .flag files?

@szymon-rd szymon-rd requested a review from prolativ January 5, 2023 11:35
@szymon-rd szymon-rd merged commit f56089b into scala:main Jan 9, 2023
@szymon-rd szymon-rd deleted the new-lazyvals-as-default branch January 9, 2023 17:18
@Kordyjan Kordyjan modified the milestones: 3.3.0-RC1, 3.3.0 Aug 1, 2023
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.

Stabilize new lazy vals
3 participants