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

Exclusive capabilities #22218

Draft
wants to merge 27 commits into
base: main
Choose a base branch
from
Draft

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Dec 16, 2024

A draft PR to implement Capybara-like mutation checking

@Linyxus
Copy link
Contributor

Linyxus commented Dec 16, 2024

scapybara

When printing a type `C^` where `C` extends `Capability`, don't show the `^`.
This is overridden under -Yprint-debug.
Add dedicated tests `isMutableVar` and `isMutableVarOrAccessor`
where we now check for the `Mutable` flag. This will allow to use
`Mutable` also for update methods, so that we don't have to burn
another flag bit for them.
Also, add design document from papers to docs/internals
This means Mutable classes get {cap.rd} as default capture set.
….toCap

If existentials are mapped to fresh, it matters where they are opened. Pure or not
arguments don't have anything to do with that.
Don't add elements to hidden sets if they were subsumed previously.
 - Always store new types on rechecking
 - Store them in a hashmap which is associated with the rechecker of the
   current compilation unit
 - After rechecking is done, the map is forgotten, unless keepTypes is true.
   Under keepTypes, then map is kept in an attachment of the unit's root tree.

Change in nomenclature:

    knownType --> nuType
    rememberType --> setNuType
    hasRememberedType --> hasNuType
@odersky odersky force-pushed the exclusive-capabilities branch from 8ae9a33 to 8cbc022 Compare December 21, 2024 11:34
 - Use unsafeAssumeSeparate(...) as an escape hatch
@odersky odersky force-pushed the exclusive-capabilities branch from 8cbc022 to 0a73a26 Compare December 21, 2024 14:01
 - In ++, use a FrozenSepState in order not to pollute hidden sets
 - This avoids two spurious separation failures in stdlib
@odersky
Copy link
Contributor Author

odersky commented Dec 21, 2024

The earliest European representation of a capybara from "A Relation of a voyage" (1698)

image

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