fix: Broken long arg inference on conflicts #4584
Conversation
Signed-off-by: Alex Saveau <[email protected]>
|
Closing as this was split out of #4583 and an issue was requested before a PR |
|
If you'd like to file an issue for me, go for it, but I will not be wasting my time when there is an obvious bug with a simple solution that's unit tested. If you end up including these commits (or any part of them), please make sure they are authored (or co-authored) by "Alex Saveau [email protected]". |
|
The point of creating issues is for communication, to make sure we understand and agree on the problem and solution before focusing on the code. |
|
@epage is the issues-first policy still a thing or can these two PRs be reopened? Saw your release today and it'd be nice to get off of my fork. |
|
Nothing has changed about needing an Issue as a place for us to communicate and make sure we understand and agree on the problem and the solution. |
|
Ok, I've got a bit of extra time this quarter: #4603 (comment) |
Long args would pick a random arg upon conflict.
About size stuff: the vec implementation is actually bigger. Vec: 773.5 KiB. Iterator: 772.9 KiB.