Skip to content

Conversation

hamzaremmal
Copy link
Member

Include the project to set up Scala-library with cc based on the new stdlib configuration.

// Add the source directories for the stdlib (non-boostrapped)
Compile / unmanagedSourceDirectories := Seq(baseDirectory.value / "src"),
Compile / unmanagedSourceDirectories += baseDirectory.value / "src-bootstrapped",
// NOTE: The only difference here is that we drop `-Werror` and semanticDB for now
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it ok to drop semanticDB?

Copy link
Member Author

Choose a reason for hiding this comment

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

It used to crash the compiler because Predef didn't include the definitions of the patched symbols. It is done in all the projects for now and will be reversed (with the other) when we do the full switch.

@hamzaremmal hamzaremmal merged commit a9c214f into scala:main Aug 5, 2025
50 of 51 checks passed
@hamzaremmal hamzaremmal deleted the cc-stdlib branch August 5, 2025 10:59
hamzaremmal added a commit that referenced this pull request Aug 7, 2025
Reverts #23662

During today's core meeting, we decided to switch the strategy of having
two separate artifacts for the stdlib (one with cc and one without cc).
We will now commit and ship **only** the stdlib with cc.
If a user enables cc, they will get the benefit of a capture-checked
stdlib, if they don't enable cc, then cc will not change anything from a
user's perspective.

Important Note: Capture Checking the stdlib doesn't mean that capture
checking is stable, it is a milestone into the development of capture
checking.
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