Compiler should catch name collision between package and file name

[janicedatawire]

The package name and the quark file name must be different. The compiler currently allows them to be the same - it should check and throw an error in this case.

[ark3]

To clarify, the package name (package henry { ... }) and the quark filename (henry.q) must be different only if the quark file contains code that is not in a package. In the JS and Python backends, that non-package code ends up in a target file named after the quark filename (henry.js and henry.py), which makes importing the package (in henry/index.js and henry/__init__.py) conflict with importing the non-package code.

The compiler could detect this scenario and then complain unconditionally, as specified above, but it might be nicer not to complain if there is no non-package code and thus no conflict. I like the idea of defining a package called directory in a file called directory.q.

[bozzzzo]

@ark3 this sounds like fixed in recent quark?

[ark3]

Quark no longer has non-namespace code. All code lives in some named namespace, so the above is no longer an issue.