You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the following would IMO be the perfect solution, allowing stdlib/compiler/tools to use nimble packages, while not clashing with user installed packages
import std/strutils # stdlibimport stdx/regex # controlled via `nimble install regex` from compiler installation, using fixed hashes for all dependent pkgsimport pkg/regex # controlled via `nimble install regex` from user; stdx/regex and pkg/regex resolve as separate modulesimport regex # same as pkg/regex
the rare case of exportc procs can be dealt with using a exportc prefix (eg "stdx") to avoid duplicate definition errors
the stdx prefix is not even essential, ie, std/regex could be used to, and modules could transparently be re-mapped to a separate nimble package without breaking user code nor interfering with user installed nimble packages (which could be a different version or same, irrelevant) ; neat.
The text was updated successfully, but these errors were encountered:
timotheecour
changed the title
stdx/regex + allow stdlib+compiler to have their own locked down, isolated nimble dependenciesstdx/regex etc: allow stdlib+compiler to have their own locked down, isolated nimble dependencies
Jul 30, 2021
timotheecour
changed the title
stdx/regex etc: allow stdlib+compiler to have their own locked down, isolated nimble dependencies
allow stdlib+compiler to have their own locked down, isolated nimble dependencies that live in a separate namespace (eg stdx/regex)
Jul 30, 2021
the following would IMO be the perfect solution, allowing stdlib/compiler/tools to use nimble packages, while not clashing with user installed packages
the rare case of
exportc
procs can be dealt with using a exportc prefix (eg "stdx") to avoid duplicate definition errorsthe stdx prefix is not even essential, ie, std/regex could be used to, and modules could transparently be re-mapped to a separate nimble package without breaking user code nor interfering with user installed nimble packages (which could be a different version or same, irrelevant) ; neat.
links
The text was updated successfully, but these errors were encountered: