-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Allow for more than 256 occurrences of an argument. #409
Conversation
Thanks for the pull request, and welcome! The team is excited to review your changes, and you should hear from @Vinatorul (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Thank you for your contribution! |
Hi, thanks for the quick review! Thanks! |
Thank you kindly! I will merge as soon as build finish. |
Looks good to me too, and this is something I've been casually thinking about for a while so thanks! 👍 @homu r+ |
📌 Commit f86a183 has been approved by |
Allow for more than 256 occurrences of an argument. Hi, I often use tools with `xargs` and the like, and it's entirely possible to end up with inhumanly long sets of parameters being passed to a command. Without this fix, the library will panic with an arithmetic overflow in `ArgMatcher#inc_occurrence_of` when the 256th instance of the parameter is accounted for. Thanks,
Allow for more than 256 occurrences of an argument. Hi, I often use tools with `xargs` and the like, and it's entirely possible to end up with inhumanly long sets of parameters being passed to a command. Without this fix, the library will panic with an arithmetic overflow in `ArgMatcher#inc_occurrence_of` when the 256th instance of the parameter is accounted for. Thanks,
☀️ Test successful - status |
Thanks for your hard work! |
Bug fixes, new setting, code clean up, and added support u64::max values per arg This turned into a little more than just a quick bug fix 😜 Thanks to #409 I've piggy backed on that and added support for > 256 values as well. There's also just a bunch of code deduping and super small macro cleanups. After this merges I'll put out 2.0.3
Bug fixes, new setting, code clean up, and added support u64::max values per arg This turned into a little more than just a quick bug fix 😜 Thanks to #409 I've piggy backed on that and added support for > 256 values as well. There's also just a bunch of code deduping and super small macro cleanups. After this merges I'll put out 2.0.3
Hi,
I often use tools with
xargs
and the like, and it's entirely possible to end up with inhumanly long sets of parameters being passed to a command.Without this fix, the library will panic with an arithmetic overflow in
ArgMatcher#inc_occurrence_of
when the 256th instance of the parameter is accounted for.Thanks,