Re:The Rust Calling Convention We Deserve
by JoshTriplett on Friday April 19, 2024 @05:03AM
(#40084660)
There's no proposal to stabilize the Rust ABI. There are proposals to define a separate stable ABI, which would not be the default ABI. (Such a separate stable ABI would want to plan for long-term performance, but the default ABI could continue to improve.)
[ Parent
| on HN ]
Re:The Rust Calling Convention We Deserve
by weinzierl on Friday April 19, 2024 @01:15PM
(#40089425)
Thanks, I never had considered that a possibility when hearing about "Rust stable ABI", but it makes a lot if sense.
Re:The Rust Calling Convention We Deserve
by zozbot234 on Friday April 19, 2024 @02:01PM
(#40090052)
There is already a separate stable ABI, it's just the C ABI. There are also multiple crates that address the issue of stable ABIs for Rust code. It's not very clear why compiler involvement would be required for this.
Re:The Rust Calling Convention We Deserve
by tialaramex on Saturday April 20, 2024 @06:16PM
(#40101494)
Surely it would be nice to be able to specify using the repr mechanism that you explicitly want so-and-such ABI, in the same way that you can for the C ABI.
I haven't looked at the crates you're describing, but presumably they're providing a proc macro or something instead, which is not really the right layer to do this stuff.