Inconsistent names resolution #6026
Unanswered
vitvakatu
asked this question in
Work In Progress - Engine
Replies: 1 comment
-
|
I made an issue #5616 AFAIK the "Main" name should not be used in code at all. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I'm developing recognition of qualified names in CB and faced a weird behavior of the engine.
I have a project named
Unnamed_14with the submoduleFoowith the methodfoo. I also havefunc1defined in theMainmodule of the project.func1, I have expected results – I can call it by the fully qualified namelocal.Unnamed_14.func1, and I can import any part of the name and make it shorter.local.Unnamed_14.Main.func1does not work though. It seems inconsistent, as I can callMain.func1. It fails withmethod Main of Main could not be found.fooby a fully qualified name. It works withfunc1, so it is inconsistent. It fails withmethod Foo of Main could not be found.I wonder what the correct behavior in such cases is. Do we have any bugs here, or it is all working as designed?
Unnamed_14.zip
Beta Was this translation helpful? Give feedback.
All reactions