Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

Field names on classes somehow interfere with return types #245

Open
itamarst opened this issue Aug 8, 2016 · 0 comments
Open

Field names on classes somehow interfere with return types #245

itamarst opened this issue Aug 8, 2016 · 0 comments

Comments

@itamarst
Copy link
Contributor

itamarst commented Aug 8, 2016

If you have a field on a class that has same name as a namespace this can interfere with compilation of methods that try to refer to that namespace.

bash-4.3# quark compile --python test.q
Checking environment ... done.
Parsing: test.q ....
Compiling quark code ...

/code/test.q:6:11: unresolved variable: Promise

bash-4.3# cat test.q
quark *;

class MyClass {
    String quark; // <--- ONO IT IS THE SAME NAME AS A NAMESPACE

    quark.Promise foo() { return new PromiseFactory().promise; }
}

The error message is also confusing and irrelevant.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant