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

Remove CyclicInitializationError from Dart Language Specification #2720

Closed
sgrekhov opened this issue Dec 14, 2022 · 3 comments
Closed

Remove CyclicInitializationError from Dart Language Specification #2720

sgrekhov opened this issue Dec 14, 2022 · 3 comments
Assignees
Labels
bug There is a mistake in the language specification or in an active document

Comments

@sgrekhov
Copy link
Contributor

CyclicInitializationError is deprecated and removed from Dart 3.0. But Dart Language specification still has a reference to CyclicInitializationError

a \code{CyclicInitializationError} is thrown.

@sgrekhov sgrekhov added the bug There is a mistake in the language specification or in an active document label Dec 14, 2022
@lrhn
Copy link
Member

lrhn commented Dec 14, 2022

I believe that's because the null-safety patch to the specification has not yet landed. There is also no reference to late in the linked section.

The null safe behavior is to recurse infinitely on cyclic references in late/lazy variables, so no replacement error has been specified. (And repeat-assignment to late final variables is an unspecified error.)

@eernstg
Copy link
Member

eernstg commented Dec 14, 2022

I believe that's because the null-safety patch to the specification has not yet landed.

Exactly, this change has already been performed in #2605.

But, in order to get #2605 landed we could take it one word at a time. ;-) @lrhn, perhaps we should just make all those small changes in tiny PRs as they come up? With a rebase across each of these tiny PRs, #2605 will simply get smaller and smaller because we have just done one small piece of it.

@eernstg
Copy link
Member

eernstg commented Mar 23, 2023

I'll close this issue because the requested change is part of the upcoming null safety updates performed in #2605.

@eernstg eernstg closed this as completed Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug There is a mistake in the language specification or in an active document
Projects
None yet
Development

No branches or pull requests

3 participants