Dominik Picheta

> If it's harmless enough for "git clone", it's harmless enough for Nimble. Simple. You might very well install local Nimble packages, and then you'll get all sorts of generated...

@timotheecour I love it. Let's do it :) Edit: Actually, thinking about it some more. This will break packages like `jester` which allow you to just `import jester`, you'll need...

@Araq Are macros supposed to be callable from this context?

Perhaps we need a way to define what contexts a macro can be invoked in? On Mon, Sep 7, 2015 at 3:18 PM, Andreas Rumpf [email protected] wrote: > Yeah but...

Yeah, precisely. Although there is definitely room here to change this. Problem is that there are times when the git tag version doesn't match the .nimble file's version info :)

This is indeed weird. I think it might be a Nim bug: https://github.com/nim-lang/Nim/issues/8773

Sure, this would be nice. As a side note: ```nim import pkg/[jester] ``` I really wish you would just use ``import jester``.

> that's to avoid symbol clashes (cf rationale why std and pkg were introduced) All new modules in the stdlib are added to a mandatory `std` dir. You don't need...

Nope. But I won't allow such packages to be published. On Thu, 1 Nov 2018, 21:50 Timothee Cour, wrote: > > - does nimble (not necessarily published nimble pkg) enforce...

would be nice to fix this