-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
doc
command on a module importing std/jsffi
and using a module config file (<modulename>.nims
) causes error
#21441
Comments
Fix might be to change Lines 2219 to 2221 in 6fea221
Not defining |
github-actions
bot
added
the
stale
Staled PR/issues; remove the label after fixing them
label
Jun 4, 2023
metagn
added a commit
to metagn/Nim
that referenced
this issue
Sep 18, 2024
metagn
added a commit
to metagn/Nim
that referenced
this issue
Sep 21, 2024
fixes nim-lang#21441 When compiling for JS, nimscript config files have both `defined(js)` and `defined(nimscript)` be true at the same time. This is required so that the nimscript config file knows the current compilation is for the JS backend. However the system module doesn't account for this in some cases, defining JS-specific code or not defining nimscript-specific code when compiling such nimscript files. To fix this, have the `nimscript` define take priority over the `js` one.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Running
doc
command on a module importingstd/jsffi
and using a module config file (<modulename>.nims
) causes error.Failing Examples
module.nim
module.nims
# empty
Error
module.nim
module.nims
--backend:js
Error
Passing Examples
module.nim
module.nimsNim Version
1.6.10
1.9.1-642136ec4f2cd93cdd753bf16fa4aec89b8fee82
Current Output
No response
Expected Output
No response
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: