about summary refs log tree commit diff
path: root/tests/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
diff options
context:
space:
mode:
authorJubilee <46493976+workingjubilee@users.noreply.github.com>2024-06-12 03:57:19 -0700
committerGitHub <noreply@github.com>2024-06-12 03:57:19 -0700
commit969056dd8ca6827a37af58720ba3ca7ae7447da0 (patch)
treec30bba38047976a613f4e72945ff6950d7324a3f /tests/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
parent8d3b9a19cfdf5ee0561e43f3176d9501bcf2c4d9 (diff)
parentc8a36979e6410058ec359ce6abf68077b3237116 (diff)
downloadrust-969056dd8ca6827a37af58720ba3ca7ae7447da0.tar.gz
rust-969056dd8ca6827a37af58720ba3ca7ae7447da0.zip
Rollup merge of #124514 - michaelwoerister:zero-disambiguator-demangling-recommendation, r=davidtwco
Recommend to never display zero disambiguators when demangling v0 symbols

This PR extends the [v0 symbol mangling documentation](https://doc.rust-lang.org/rustc/symbol-mangling/v0.html) with the strong recommendation that demanglers should never display zero-disambiguators, especially when dealing with `crate-root`.

Being able to rely on `C3foo` to be rendered as `foo` (i.e. without explicit disambiguator value) rather than as `foo[0]` allows the compiler to encode things like new basic types in a backward compatible way. This idea has been originally proposed by `@eddyb` in [the discussion around supporting `f16` and `f128` in the v0 mangling scheme](https://github.com/rust-lang/rust/pull/122106). It is a generally useful mechanism for supporting a certain class of new elements in the v0 mangling scheme in a backward compatible way (whether as a temporary workaround until downstream tooling has picked up grammar changes or as a permanent encoding).

cc `@tgross35`
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions