Exclusive Capabilities #22577
Draft
Exclusive Capabilities #22577
+4,055
−738
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add Mutable trait and mut modifier.
- Add dedicated tests `isMutableVar` and `isMutableVarOrAccessor`
so that update methods can share the same flag `Mutable` with mutable vars.
- Disallow update methods overriding normal methods
- Disallow update methods which are not members of classes extending Mutable
- Add design document from papers repo to docs/internals
- Add readOnly capabilities
- Implement raeadOnly access
- Check that update methods are only called on references with exclusive capture sets.
- Use cap.rd as default capture set of Capability subtypes
- Make Mutable a Capability, this means Mutable class references get {cap.rd} as
default capture set.
- Use {cap} as captu
….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.
These are represented as Fresh.Cap(hidden) where hidden is the set of
capabilities subsumed by a fresh. The underlying representation is as
an annotated type `T @annotation.internal.freshCapability`.
Require -source `3.7` for caps to be converted to Fresh.Cap
Also:
- Refacture and document CaputureSet
- Make SimpleIdentitySets showable
- Refactor VarState
- Drop Frozen enum
- Make VarState subclasses inner classes of companion object
- Rename them
- Give implicit parameter VarState of subCapture method a default value
- Fix printing of capturesets containing cap and some other capability
- Revise handing of @uncheckedAnnotation
Check separation from source 3.7 on. We currently only check applications, other areas of separation checking are still to be implemented.
Check that a capability that gets hidden in the (result-)type of some definition is not used afterwards in the same or a nested scope.
When checking whether two items overlap we should always check their deep capture sets. Buried aliases should count as well.
This is necessary since capability sets are IdentitySets.
Downgrade to -source 3.6 to turn it off.
Allow them only in @consume methods
Also: Fixes to computations of overlapWith and -- on Refs that take account of pathss, where shorter paths cover deeper ones.
Use a coarser prediction of hidden sets. Any Fresh.Cap instance in a capture set means that we should do the hidden check. Previously this was the case only if the Fresh.Cap instance hid something non maximal, element, but only directly, not via another Cap. Another version searched for non-maximal references deeply, but this one caused infinite looping in the CI. But in any case it's fine to over-approximate and assume that any Fresh.Cap hides something.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.