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

Explain the reason for support parsing legacy restricted types #3614

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Explain the reason for support parsing legacy restricted types #3614

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
6 changes: 3 additions & 3 deletions runtime/parser/type.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -479,9 +479,9 @@ func defineIntersectionOrDictionaryType() {
},
)

// While restricted types have been removed from Cadence, during the first few months of the
// migration period, leave a special error in place to help developers
// TODO: remove this after Stable Cadence migration period is finished
// Though the restricted types were removed starting with Cadence v1.0,
// still try to parse restricted types if present, and report a proper error.
// This is to give meaningful error messages for anyone trying pre-1.0 codes.
setTypeMetaLeftDenotation(
lexer.TokenBraceOpen,
func(p *parser, rightBindingPower int, left ast.Type) (result ast.Type, err error, done bool) {
Expand Down
Loading