Update tendril

[ehuss]

The 0.4.1 version of tendril (used by mdbook) triggers the unaligned_references lint which is now reported as a future-compatibility warning as of #95372. This updates it to 0.4.3 which does not trigger the warning. This update also triggered the update of futf from 0.1.4 to 0.1.5.

tendril changes: servo/tendril@v0.4.1...v0.4.3
futf changes: servo/futf@v0.1.4...v0.1.5

[rust-highfive]

r? @Mark-Simulacrum

(rust-highfive has picked a reviewer for you, use r? to override)

[ehuss]

@Mark-Simulacrum I'm curious if you have any opinions about somehow denying these warnings? It is not currently possible AFAIK, but it might be helpful to uncover these hidden warnings.

[Mark-Simulacrum]

Do you have a reference/link for how to reproduce the warning?

Maybe we could use the force lint level to bypass cap-lints...

I'm a little worried that we might experience these lints during beta bumps in practice (when they're newly introduced via bootstrap tools), which seems like a bad time for them to appear... normally new lints are in-tree so we can easily enough fix them, but in dependencies that's not the case.

One solution could be toolstate-like denies, maybe.

[Mark-Simulacrum]

r=me on the PR itself though

[ehuss]

./x.py build src/tools/rustbook --stage=0 will show the warning. It looks like this:

warning: the following packages contain code that will be rejected by a future version of Rust: tendril v0.4.1
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`

-F unaligned_references doesn't work because of the way it interacts with --cap-lints (cap-lints "wins").

I think in order to deny these warnings, there will either need to be something added to rustc or cargo. I'm guessing cargo. I think my idea was to have the ability to control lint levels from cargo, and have this be just another control (like "deny" cargo::future_incompat). Unfortunately that project has been stuck for a while (rust-lang/cargo#5034).

I'm not sure what is meant by "toolstate-like denies". If that is something like "future-incompat warnings exist" is an entry in the toolstate database, that would help with exposing the warnings more visibly. I'm not sure how that could work. Unfortunately Cargo doesn't emit any sort of JSON messages to help here.

The hope was that these kinds of warnings would be extremely rare, but perhaps that was wishful thinking on my part.

@bors r=Mark-Simulacrum

[bors]

📌 Commit 04b75a7 has been approved by Mark-Simulacrum

[bors]

🌲 The tree is currently closed for pull requests below priority 1000. This pull request will be tested once the tree is reopened.