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
When it is a lib dependency, it now assume all the code written in the lib.no.
It would be better if it allow the lib.no to instruct processing of other files.
For example, given lib.no:
use comparator;use bits;
Then the compiler can look for the comparator.no and bits.no files in the package folder, and include them to be part of pipeline, instead of only taking care of lib.no
The text was updated successfully, but these errors were encountered:
note that maybe going the golang way would be interesting? (any .go file under the same folder is accessible without importing, like it's all part of the same file)
When it is a lib dependency, it now assume all the code written in the
lib.no
.It would be better if it allow the
lib.no
to instruct processing of other files.For example, given
lib.no
:Then the compiler can look for the
comparator.no
andbits.no
files in the package folder, and include them to be part of pipeline, instead of only taking care oflib.no
The text was updated successfully, but these errors were encountered: