You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A potential fix would be to flag the import in part4 as low priority, resulting in a more consistently correct order of processing of the cycle (see #2015 for a discussion of this).
Another, likely less nice fix would be to run the semantic analysis pass that resolves from ... import ... statements within a cycle multiple times somehow, until all imports have been resolved.
The text was updated successfully, but these errors were encountered:
The following code generates an unexpected error message:
Here's what I get when I try to type check it:
If I change the order of modules the error won't occur (
part{1,3,2,4}.py
), as it depends on the order in which we process the cycle.This is related to #2015.
A potential fix would be to flag the import in
part4
as low priority, resulting in a more consistently correct order of processing of the cycle (see #2015 for a discussion of this).Another, likely less nice fix would be to run the semantic analysis pass that resolves
from ... import ...
statements within a cycle multiple times somehow, until all imports have been resolved.The text was updated successfully, but these errors were encountered: