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
I also have a PR that turns nimscript into an import module (not include file) and allows a nimscript module to skip auto-importing it, which makes nims code more like regular nim code without all the "baggage" like cd, etc. I just need to see how well it fits with nim-lang#14235.
related: as mentioned in nim-lang#14143 (comment)
implicitly exported symols are not good, in particular when they differ from standard nim c behavior
user should import os for these and it'd work via vmops
we should be able to do this without much breakage by introducing a flag --nimsimports:off with semantics:
--nimsimports:off # doesn't import anything, user has to import relevant module (eg os); will be default in some future tag 1.3.X
--nimsimports:on # default until 1.3.x, gives a new warning while it's on
The text was updated successfully, but these errors were encountered:
related: as mentioned in nim-lang#14143 (comment)
implicitly exported symols are not good, in particular when they differ from standard nim c behavior
user should import os for these and it'd work via vmops
we should be able to do this without much breakage by introducing a flag --nimsimports:off with semantics:
--nimsimports:off # doesn't import anything, user has to import relevant module (eg os); will be default in some future tag 1.3.X
--nimsimports:on # default until 1.3.x, gives a new warning while it's on
The text was updated successfully, but these errors were encountered: