Package compiler as such

[arnetheduck]

Description

In addition to the compiler not being available via nimble, the compiler packaging as exposed by the nimble file is inconvenient to import.

Because of name conflicts, the compiler should ideally be packaged such that imports include compiler/ to disambiguate packages such as compiler/options, else it becomes hard to use it in tooling.

Having access to the compiler code in tooling is important - at the same time, it is very inefficient for tooling to follow the same slow release cycle as the compiler / language itself.

Nim Version

devel

Current Output

No response

Expected Output

No response

Possible Solution

No response

Additional Information

No response

[beef331]

One can do import "$nim" / compiler /.... which will use the compiler source that is with whatever Nim compiler is being used(assuming it's in the right directory and shipped with the compiler).

[arnetheduck]

with whatever Nim compiler

ooh, that's a nice hack / workaround - however, tooling will typically require a very specific version of the compiler source code - ideally the one it actually asks for in the nimble file which doesn't necessarily have to be the same as the one being used for compilation.

Ideally, the compiler would be a library just like any other dependency so that the really most basic tooling works with it, starting with its use in a package manager.