-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix regression that broke string.format with list objects #9532
fix regression that broke string.format with list objects #9532
Conversation
String formatting should validly assume that printing a list means printing the list itself. Instead, something like this broke: 'one is: @0@ and two is: @1@'.format(['foo', 'bar'], ['baz']) which would evaluate as: 'one is: foo and two is: bar' or: 'the value of array option foobar is: @0@'.format(get_option('foobar')) which should evaluate with '-Dfoobar=[]' as 'the value of array option foobar is: []' But instead produced: meson.build:7:0: ERROR: Format placeholder @0@ out of range. Fixes mesonbuild#9530
Codecov Report
@@ Coverage Diff @@
## master #9532 +/- ##
==========================================
- Coverage 67.41% 67.39% -0.03%
==========================================
Files 396 396
Lines 85562 85564 +2
Branches 17665 17665
==========================================
- Hits 57684 57665 -19
- Misses 23214 23243 +29
+ Partials 4664 4656 -8
Continue to review full report at Codecov.
|
This is configured as:
but apparently it now works? Do you know why, or if it is expected to stay that way? (I genuinely have no idea when tests are/were expected to be skipped, or why, to begin with.) |
I guess you mean Why was it skipped in the first place? |
ah, I'd guess this is msys2/MINGW-packages@345fe43 which got uploaded 4 days ago, so likely fixed and can be unskipped. |
See mesonbuild#9532 (comment) for context. It's unclear why this was skipped exactly in the first place, but it started to pass recently and MSYS2 fixed some cmake+llvm related things in msys2/MINGW-packages@345fe43 at the same time, so this is likely the reason.
I've created #9534 |
String formatting should validly assume that printing a list means printing the list itself. Instead, something like this broke:
which would evaluate as:
or:
which should evaluate with '-Dfoobar=[]' as
But instead produced:
Fixes #9530