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
Nimble has a major flaw, which is it applies all the packages it has on every project you have by default. That's my major concern that easy can create a mess if not considered.
I will give you an example exactly with nimtorch:
Have nimtorch installed as nimble package
Also work on the repository
Did not run nimble develop
Rename a file in the repository
Forget to update the module import myrenamedfile into import newlocation/myrenamedfile
Build will succeed yet will use import myrenamedfile from nimble this time..
but it all works if you run nimble develop, right? I think that's expected and I don't see a limitation here (in the sense of making it impossible to do certain things).
if you really feel something is ill-designed with nimble it really should be a bug report in https://github.com/nim-lang/nimble/issues/ otherwise it will never get fixed (if there's anything to fix).
That being said, one possibility would be (and that's doable, not a fundamental flaw IMO):
if you call nimble build inside a local package foo, nimble could remove from search path an installed package named foo
The text was updated successfully, but these errors were encountered:
Well honestly I don't think that's really good (the nimble develop thing). It's easy to forget sometimes and specially hard to understand for new users.
Imho should be default to have packages bound to the project folder somehow or have environments like conda.
Another very confusing point is package versions, afaik nimble keeps all versions you fetch on disk but anyway it will always use the head ignoring nimble file specs. ( correct me if you figured the arcane behind this, I did not really dig )
Finally yes, hardly documented.
Anyway not supporting binaries and using a .json file as db does not fit our needs really.
Oh and I think Araq is not a fan either so much https://github.com/Araq/nawabs
Btw if you don't mind I'll close the issue just cos not so related to nimtorch.
That said, it's a good tool and still very useful, just I suspect it's slowly collecting dust and it seems that noone wants to take care of it much.
moved to here the discussion started here #6 (comment) to keep each topic separate
@sinkingsugar
but it all works if you run
nimble develop
, right? I think that's expected and I don't see a limitation here (in the sense of making it impossible to do certain things).if you really feel something is ill-designed with nimble it really should be a bug report in https://github.com/nim-lang/nimble/issues/ otherwise it will never get fixed (if there's anything to fix).
That being said, one possibility would be (and that's doable, not a fundamental flaw IMO):
if you call
nimble build
inside a local packagefoo
, nimble could remove from search path an installed package namedfoo
The text was updated successfully, but these errors were encountered: