diff options
| author | bors <bors@rust-lang.org> | 2025-02-12 09:44:30 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-02-12 09:44:30 +0000 |
| commit | 021fb9c09a19d206a37226fe6168f1cc7c984925 (patch) | |
| tree | 47fdc7db18f73b8d69b6093f2322c873ae11f35e /src | |
| parent | 33d92df3e6552a91ace2594eb7a2e1dc0c3e37fb (diff) | |
| parent | cafa646f21ec41d6b20b5495c25456c997206dc1 (diff) | |
| download | rust-021fb9c09a19d206a37226fe6168f1cc7c984925.tar.gz rust-021fb9c09a19d206a37226fe6168f1cc7c984925.zip | |
Auto merge of #136897 - workingjubilee:revert-unfcped-stab, r=WaffleLapkin
Revert "Stabilize `extended_varargs_abi_support`" I cannot find an FCP for this, despite it being a stabilization PR which normally means we do an FCP of some kind? It would seem reasonable for _either_ compiler or lang to have FCPed it? I am thus opening a revert PR, which mostly-cleanly applies, so that we can later actually land this properly with a stability report and FCP. - https://github.com/rust-lang/rust/issues/136896 - https://github.com/rust-lang/rust/pull/116161 - https://github.com/rust-lang/rust/issues/100189
Diffstat (limited to 'src')
| -rw-r--r-- | src/doc/unstable-book/src/language-features/extended-varargs-abi-support.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/src/doc/unstable-book/src/language-features/extended-varargs-abi-support.md b/src/doc/unstable-book/src/language-features/extended-varargs-abi-support.md new file mode 100644 index 00000000000..b20c30ec8f1 --- /dev/null +++ b/src/doc/unstable-book/src/language-features/extended-varargs-abi-support.md @@ -0,0 +1,10 @@ +# `extended_varargs_abi_support` + +The tracking issue for this feature is: [#100189] + +[#100189]: https://github.com/rust-lang/rust/issues/100189 + +------------------------ + +This feature adds the possibility of using `sysv64`, `win64` or `efiapi` calling +conventions on functions with varargs. |