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.

Sign up for GitHub

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

Add note about migration changes to entitlements migration #252

Merged
merged 1 commit into from
Mar 6, 2024
Merged

Add note about migration changes to entitlements migration #252

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions cadence/20230601-entitlements-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ The challenge here is that it is not possible to determine what entitlements the

## Proposed Solution

NB: this solution has since been updated and iterated upon slightly to address issues that came up during its implementation. See https://cadence-lang.org/docs/cadence_migration_guide/type-annotations-guide for more details.

### `Entitlements(T)`

The first part of this solution involves the definition of an informal “function” on types, called `Entitlements`. For some type `T` that exists in pre-Stable Cadence, `Entitlements(T)` expresses the set of entitlements necessary post-Stable Cadence contract update that are necessary to call the same set of members that were previously accessible to a reference typed `&{T}`.
Expand Down
Loading