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

Handle flags correctly for nimble run #927

Merged
merged 1 commit into from
Jul 4, 2021
Merged

Handle flags correctly for nimble run #927

merged 1 commit into from
Jul 4, 2021

Conversation

shunf4
Copy link
Contributor

@shunf4 shunf4 commented Jul 3, 2021

  1. check for isGlobalFlag before setRunOptions. Flags like --debug should not be treated as run options.
  2. in handleUnknownFlags, add unknown flags to compileFlags instead of overwriting compileFlags. This enables compilation flags after the run command to be correctly passed.

Fixes #923.

1. check for `isGlobalFlag` before `setRunOptions`. Flags like `--debug`
   should not be treated as `run` options.
2. in `handleUnknownFlags`, add unknown flags to `compileFlags`
   instead of overwriting `compileFlags`.
   This enables compilation flags after the `run` command to be correctly
   passed.
@shunf4
Copy link
Contributor Author

shunf4 commented Jul 3, 2021

@konsumlamm

Copy link
Collaborator

@dom96 dom96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but damn the amount of possibilities this adds is making me nervous :)

@dom96 dom96 merged commit 919e201 into nim-lang:master Jul 4, 2021
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

Successfully merging this pull request may close these issues.

Compiler options for nimble run are not passed (again)
2 participants