diff options
| author | bors <bors@rust-lang.org> | 2025-04-19 08:01:53 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-04-19 08:01:53 +0000 |
| commit | a7c39b68616668a45f0afd62849a1da7c8ad2516 (patch) | |
| tree | ef0cc1f7acb8d26d920aaa02a328386b65e5659b /compiler/rustc_codegen_cranelift/example/std_example.rs | |
| parent | 2ef78586529b5f68cc42bcbe9b10b4afe56a942a (diff) | |
| parent | 5523c87c41b357fe3c3047dabf603f18830eeaf8 (diff) | |
| download | rust-a7c39b68616668a45f0afd62849a1da7c8ad2516.tar.gz rust-a7c39b68616668a45f0afd62849a1da7c8ad2516.zip | |
Auto merge of #139114 - m-ou-se:super-let-pin, r=davidtwco
Implement `pin!()` using `super let` Tracking issue for super let: https://github.com/rust-lang/rust/issues/139076 This uses `super let` to implement `pin!()`. This means we can remove [the hack](https://github.com/rust-lang/rust/pull/138717) we had to put in to fix https://github.com/rust-lang/rust/issues/138596. It also means we can remove the original hack to make `pin!()` work, which used a questionable public-but-unstable field rather than a proper private field. While `super let` is still unstable and subject to change, it seems safe to assume that future Rust will always have a way to express `pin!()` in a compatible way, considering `pin!()` is already stable. It'd help [the experiment](https://github.com/rust-lang/rust/issues/139076) to have `pin!()` use `super let`, so we can get some more experience with it.
Diffstat (limited to 'compiler/rustc_codegen_cranelift/example/std_example.rs')
0 files changed, 0 insertions, 0 deletions