Skip to content

Commit 30b477a

Browse files
Add a recommended resolution for open question around encoding function parameter types.
1 parent f8e3ab6 commit 30b477a

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

text/0000-symbol-name-mangling-v2.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1023,6 +1023,13 @@ does not propose to do this because:
10231023

10241024
However, a final decision on the topic has not been made yet.
10251025

1026+
**UPDATE**: This RFC suggests that parameter types are *not* encoded into
1027+
function and method symbols. Symbol names will already get significantly
1028+
longer due to encoding additional information and the additional
1029+
safeguard provided against ABI mismatches is less relevant for Rust
1030+
than it is for other languages that don't have a concept of
1031+
library/crate metadata.
1032+
10261033

10271034
# Appendix A - Suggested Demangling
10281035

@@ -1146,3 +1153,4 @@ pub static QUUX: u32 = {
11461153
- Added note about Punycode making decoding more complicated.
11471154
- Resolve question of complex constant data.
11481155
- Add a recommended resolution for open question around Punycode identifiers.
1156+
- Add a recommended resolution for open question around encoding function parameter types.

0 commit comments

Comments
 (0)