Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

send pr_nimscript_module PR #307

Open
timotheecour opened this issue Jun 16, 2020 · 0 comments
Open

send pr_nimscript_module PR #307

timotheecour opened this issue Jun 16, 2020 · 0 comments

Comments

@timotheecour
Copy link
Owner

timotheecour commented Jun 16, 2020

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

@timotheecour timotheecour changed the title send pr_nimscript_module send pr_nimscript_module PR Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant