Skip to content

Drop reach capabilities#26246

Draft
odersky wants to merge 5 commits into
scala:mainfrom
dotty-staging:drop-reach
Draft

Drop reach capabilities#26246
odersky wants to merge 5 commits into
scala:mainfrom
dotty-staging:drop-reach

Conversation

@odersky
Copy link
Copy Markdown
Contributor

@odersky odersky commented Jun 6, 2026

Based on #26193

  • Change or disable reach capability tests
  • Drop deprecated features of cap
  • Drop generation of reach capabilties
  • Drop types and infrastructure for reach capabilities

@odersky odersky requested a review from a team as a code owner June 6, 2026 14:30
@odersky odersky marked this pull request as draft June 6, 2026 14:30
odersky added 4 commits June 7, 2026 20:04
This should help with keeping error messages more focused.

I noted that programs that have regular capture check errors sometimes have strange
leakage and separation errors in addition. We now suppress these and issue them only
if all regular capture check errors are resolved.
Some went undetected before. And the logic that allowed
uses inside boxing environments was missing.
If a test can be rewritten using capset variables, do that, otherwise move to
tests/disabled/reaches.
Disable withReachCaptures
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.

1 participant