I forgot to mention that the main way to work around this limitation has to
do with separating declarations of types shared by the two otherwise
circularly importing packages. But it gets tricky again then when it comes
to defining methods on the types, because you can't declare methods on
The main reason for the prohibition against circular imports is that you
have to add overhead in the processing to determine when to stop. From an
architectural perspective it also makes sense - most often if you stop for
a moment and think about what you are building, usually if you are
Hi Michel,
Maybe it would help if you gave an example of some code that you think
requires circular imports and we can see if it can be restructured without?
(IMO forbidding circular imports is a great strength!)
Kind regards,
Jamie
On Thursday, November 29, 2018 at 1:23:04 PM UTC, Michel
