-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! Just a minor cleanup issue I spotted.
@gnidan Should I add test case for --compile-none flag scenario ? |
@gnidan @CruzMolina Pleeeease ;) |
Ended up taking a different approach, but this should be done now as of #3208. Sorry for the radio silence here, but I think this PR can now be closed, since that functionality now exists! |
All my work for nothing. |
I'm really sorry about that @robertmagier! I felt awful but still decided that the alternate approach was simple enough. Looking at this again now, however, I think your tests will provide lots of value! I'll reopen this with the plan to get these tests merged, at least! |
Some of this work was taken and used in #3335. I gave coauthoring credit to @robertmagier. Apologies @robertmagier for letting this one become irrelevant :( |
I am sorry for whining ;) Thank you for giving coauthoring credit to me as well. Let me know if you need any help here... or there. |
It's no problem :) I hate to have good work go to waste, it has been a busy time the last year or so but we have implemented some process to help us to stay on top of contributions like this one. Is your Windows CI PR still relevant? |
So this feature was merged in this PR and should be released next week! |
Closing as this feature was released in version 5.1.47. Thanks! |
I throw an error when flags --compile-all or --debug are used together with -compile-none
Not sure if this is the correct way to do it.