https://github.com/rust-lang/rust/blob/ebbe63891f1fae21734cb97f2f863b08b1d44bf8/tests/run-make/translation/Makefile has a test comment and test case:
|
# Check that a primary bundle with a broken message (e.g. a interpolated |
|
# variable is missing) will use the fallback bundle. |
|
missing: test.rs missing.ftl |
|
$(RUSTC) $< -Ztranslate-additional-ftl=$(CURDIR)/missing.ftl 2>&1 | $(CGREP) "struct literal body without path" |
Ignoring that this is using the wrong .ftl file (it should be using broken.ftl to correspond to the test comment, where broken.ftl contains a slug that has a stray fluent interpolation argument), this must have regressed over the years because
rustc test.rs -Ztranslate-additional-ftl=broken.ftl
actually ICEs locally due to
thread 'rustc' panicked at compiler/rustc_errors/src/emitter.rs:1465:84:
called `Result::unwrap()` on an `Err` value: failed while formatting fluent string `parse_struct_literal_body_without_path`:
the fluent string has an argument `foo` that was not found.
help: no arguments are available
Pinging back to #132181.
I assume this is not the intended behavor.
https://github.com/rust-lang/rust/blob/ebbe63891f1fae21734cb97f2f863b08b1d44bf8/tests/run-make/translation/Makefile has a test comment and test case:
rust/tests/run-make/translation/Makefile
Lines 23 to 26 in ebbe638
Ignoring that this is using the wrong
.ftlfile (it should be usingbroken.ftlto correspond to the test comment, wherebroken.ftlcontains a slug that has a stray fluent interpolation argument), this must have regressed over the years becauseactually ICEs locally due to
Pinging back to #132181.
I assume this is not the intended behavor.