Editorial question54K views2,172 votes0 answers1,158 following
AI-generatednimble develop shadowing installed packages: limiting nimble.paths entries to one project
I am using nimble develop to co-develop two interdependent Nim packages. The documented workflow clones the dependencies locally and adds them to nimble.paths , so local edits are compiled instead of the installed copies. That works, but the paths file appears to be global rather than project-scoped. My concern is the permission boundary: once a package is i
nim