date: fix subfmt-up1, fill-1, pct-pct, and invalid-high-bit-set tests / implement --debug#10940
Conversation
|
GNU testsuite comparison: |
src/uu/date/src/format_modifiers.rs
Outdated
| //! Format: `%[flags][width]specifier` | ||
| //! | ||
| //! ### Flags | ||
| //! - `-`: Left-align (pad with spaces on the right) |
There was a problem hiding this comment.
I think this flag is incorrect, when I'm testing with different - modifiers It appears to be suppressing all padding
src/uu/date/src/format_modifiers.rs
Outdated
| return result; | ||
| } | ||
|
|
||
| let pad_char = if flags.contains('0') { |
There was a problem hiding this comment.
This might be better for a follow up but I think the logic here is a bit more complicated since the pad char can be dependent on the specifier. When I'm running different modifiers locally I am sometimes seeing that the ordering of the modifiers themselves like doing _+
Merging this PR will degrade performance by 39.09%
Performance Changes
Comparing Footnotes
|
|
GNU testsuite comparison: |
|
Bravo 🥳 When you said you had a working fix for date.pl I didn't think you also had the start of the debug flag work done too. |
a43edf6 to
ae18cfc
Compare
|
GNU testsuite comparison: |
|
I'm thinking just for the sake of it being a big PR and that its net new functionality it would be better to merge then address the fixes as follow ups, once the gnu test is passing? |
|
indeed and i have a differential fuzzer ready to run :) |
|
GNU testsuite comparison: |
based on #10939
should fix tests/date/date.pl