Jacek Sieka

> Here it is the flow: why is `nimble develop` needed? `nim` should simply always be part of the lock file, just like any other dep?

> @arnetheduck I think that this feature should be held on till we tag nim version, WDYT? I believe this is the case for any nimble dependency, ie nimble will...

Ooh! This is great stuff. My plan was more or less as follows: * get it to work in any way, shape or form, with simple snippets that don't have...

> I commented a bit more than usual yeah, looking at the code with fresh eyes is an excellent opportunity to write down these lessons - if you have any...

looked a bit and it's not that simple - it may be that we need to provide memset/memcpy for now - ie even clang-8 will produce calls to this function:...

for now, I would try to just reimplement them in any way possible (ie with a loop one byte at a time) - one easy way is to add them...

updated to llvm-9 but the problem remains, so this will need an impl in nlvmbase

https://gcc.godbolt.org/z/4uAyeo

> proc dep(name: string, url: string, ver = "", rev = "") a procedural approach to lock files seems strange * what semantics would you have if you call the...

npm is mainly used to install yarn, these days ;) https://yarnpkg.com/blog/2016/11/24/lockfiles-for-all/ is a good ref on why it exists, in the first place, and what problems lock files solve.