Obscure behavior when dealing with name clashes about nelua-lang

[edubart]

What would happen if I had original tmp executable running during the compilation of the newly created tmp?

On Linux this would work fine, as Linux allows you to replace binaries that are being run, on Windows this would give a compile error, because you cannot replace running files.

On Linux this is really issue only if you try to compiler/run both files at the same time, in that situation you will may have compile errors, or run different application that you expected, this have happened with me before

I don't think it's that dangerous, this is a detail how the compiler works. If you want to avoid that you can simple use the old behavior of using nelua_cache directory instead of ~/.cache, by changing the cache_dir variable in your neluacfg.lua, you could also configure .neluacfg.lua per project basis, so you use different cache for different projects. I will state this is the official workaround.

The behavior will not change, renaming files to full path have other issues that I won't to avoid, like the file name being too long, on Windows a file path is limited to 260 characters. Also would make my life harder to locate generated files when developing Nelua (and would also for others).