Jou had this and I didn't like it. It makes you think that you can define two functions with the same name in different files, if you don't import them both into the same file. That doesn't actually work, because they go to the same binary anyway: the executable would contain both of them with the same name. Basically, Jou's import behaves more like C's #include than Python's import, and I don't want to hide that.
We could magically rename the functions based on file name, e.g. function foo() in file bar.c could be named bar_foo() in the executable. But again, I don't want to add more magic to Jou.
Jou had this and I didn't like it. It makes you think that you can define two functions with the same name in different files, if you don't import them both into the same file. That doesn't actually work, because they go to the same binary anyway: the executable would contain both of them with the same name. Basically, Jou's
importbehaves more like C's#includethan Python'simport, and I don't want to hide that.We could magically rename the functions based on file name, e.g. function
foo()in filebar.ccould be namedbar_foo()in the executable. But again, I don't want to add more magic to Jou.