Tracking Issue for RFC 3484: Unsafe Extern Blocks #123743

traviscross · 2024-04-10T20:23:23Z

This is a tracking issue for the RFC 3484: Unsafe Extern Blocks

RFC: rust-lang/rfcs#3484
Issues: F-unsafe_extern_blocks `#![feature(unsafe_extern_blocks)]`

The feature gate for the issue is #![feature(unsafe_extern_blocks)].

About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

…locks-diagnostics, r=compiler-errors Improve unsafe extern blocks diagnostics Closes rust-lang#126327 For this code: ```rust extern { pub fn foo(); pub safe fn bar(); } ``` We get ... ``` error: items in unadorned `extern` blocks cannot have safety qualifiers --> test.rs:3:5 | 3 | pub safe fn bar(); | ^^^^^^^^^^^^^^^^^^ | help: add unsafe to this `extern` block | 1 | unsafe extern { | ++++++ error[E0658]: `unsafe extern {}` blocks and `safe` keyword are experimental --> test.rs:3:9 | 3 | pub safe fn bar(); | ^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: aborting due to 2 previous errors For more information about this error, try `rustc --explain E0658`. ``` And then making the extern block unsafe, we get ... ``` error: extern block cannot be declared unsafe --> test.rs:1:1 | 1 | unsafe extern { | ^^^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: items in unadorned `extern` blocks cannot have safety qualifiers --> test.rs:3:5 | 3 | pub safe fn bar(); | ^^^^^^^^^^^^^^^^^^ error[E0658]: `unsafe extern {}` blocks and `safe` keyword are experimental --> test.rs:3:9 | 3 | pub safe fn bar(); | ^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: aborting due to 3 previous errors For more information about this error, try `rustc --explain E0658`. ``` r? `@compiler-errors`

…locks-diagnostics, r=compiler-errors Improve unsafe extern blocks diagnostics Closes rust-lang#126327 For this code: ```rust extern { pub fn foo(); pub safe fn bar(); } ``` We get ... ``` error: items in unadorned `extern` blocks cannot have safety qualifiers --> test.rs:3:5 | 3 | pub safe fn bar(); | ^^^^^^^^^^^^^^^^^^ | help: add unsafe to this `extern` block | 1 | unsafe extern { | ++++++ error[E0658]: `unsafe extern {}` blocks and `safe` keyword are experimental --> test.rs:3:9 | 3 | pub safe fn bar(); | ^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: aborting due to 2 previous errors For more information about this error, try `rustc --explain E0658`. ``` And then making the extern block unsafe, we get ... ``` error: extern block cannot be declared unsafe --> test.rs:1:1 | 1 | unsafe extern { | ^^^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: items in unadorned `extern` blocks cannot have safety qualifiers --> test.rs:3:5 | 3 | pub safe fn bar(); | ^^^^^^^^^^^^^^^^^^ error[E0658]: `unsafe extern {}` blocks and `safe` keyword are experimental --> test.rs:3:9 | 3 | pub safe fn bar(); | ^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: aborting due to 3 previous errors For more information about this error, try `rustc --explain E0658`. ``` r? ``@compiler-errors``

Rollup merge of rust-lang#127106 - spastorino:improve-unsafe-extern-blocks-diagnostics, r=compiler-errors Improve unsafe extern blocks diagnostics Closes rust-lang#126327 For this code: ```rust extern { pub fn foo(); pub safe fn bar(); } ``` We get ... ``` error: items in unadorned `extern` blocks cannot have safety qualifiers --> test.rs:3:5 | 3 | pub safe fn bar(); | ^^^^^^^^^^^^^^^^^^ | help: add unsafe to this `extern` block | 1 | unsafe extern { | ++++++ error[E0658]: `unsafe extern {}` blocks and `safe` keyword are experimental --> test.rs:3:9 | 3 | pub safe fn bar(); | ^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: aborting due to 2 previous errors For more information about this error, try `rustc --explain E0658`. ``` And then making the extern block unsafe, we get ... ``` error: extern block cannot be declared unsafe --> test.rs:1:1 | 1 | unsafe extern { | ^^^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: items in unadorned `extern` blocks cannot have safety qualifiers --> test.rs:3:5 | 3 | pub safe fn bar(); | ^^^^^^^^^^^^^^^^^^ error[E0658]: `unsafe extern {}` blocks and `safe` keyword are experimental --> test.rs:3:9 | 3 | pub safe fn bar(); | ^^^^ | = note: see issue rust-lang#123743 <rust-lang#123743> for more information = help: add `#![feature(unsafe_extern_blocks)]` to the crate attributes to enable error: aborting due to 3 previous errors For more information about this error, try `rustc --explain E0658`. ``` r? ``@compiler-errors``

…-blocks, r=compiler-errors Stabilize unsafe extern blocks (RFC 3484) # Stabilization report ## Summary This is a tracking issue for the RFC 3484: Unsafe Extern Blocks We are stabilizing `#![feature(unsafe_extern_blocks)]`, as described in [Unsafe Extern Blocks RFC 3484](rust-lang/rfcs#3484). This feature makes explicit that declaring an extern block is unsafe. Starting in Rust 2024, all extern blocks must be marked as unsafe. In all editions, items within unsafe extern blocks may be marked as safe to use. RFC: rust-lang/rfcs#3484 Tracking issue: rust-lang#123743 ## What is stabilized ### Summary of stabilization We now need extern blocks to be marked as unsafe and items inside can also have safety modifiers (unsafe or safe), by default items with no modifiers are unsafe to offer easy migration without surprising results. ```rust unsafe extern { // sqrt (from libm) may be called with any `f64` pub safe fn sqrt(x: f64) -> f64; // strlen (from libc) requires a valid pointer, // so we mark it as being an unsafe fn pub unsafe fn strlen(p: *const c_char) -> usize; // this function doesn't say safe or unsafe, so it defaults to unsafe pub fn free(p: *mut core::ffi::c_void); pub safe static IMPORTANT_BYTES: [u8; 256]; pub safe static LINES: SyncUnsafeCell<i32>; } ``` ## Tests The relevant tests are in `tests/ui/rust-2024/unsafe-extern-blocks`. ## History - rust-lang#124482 - rust-lang#124455 - rust-lang#125077 - rust-lang#125522 - rust-lang#126738 - rust-lang#126749 - rust-lang#126755 - rust-lang#126757 - rust-lang#126758 - rust-lang#126756 - rust-lang#126973 - rust-lang#127535 - rust-lang/rustfmt#6204 ## Unresolved questions I am not aware of any unresolved questions.

Rollup merge of rust-lang#127921 - spastorino:stabilize-unsafe-extern-blocks, r=compiler-errors Stabilize unsafe extern blocks (RFC 3484) # Stabilization report ## Summary This is a tracking issue for the RFC 3484: Unsafe Extern Blocks We are stabilizing `#![feature(unsafe_extern_blocks)]`, as described in [Unsafe Extern Blocks RFC 3484](rust-lang/rfcs#3484). This feature makes explicit that declaring an extern block is unsafe. Starting in Rust 2024, all extern blocks must be marked as unsafe. In all editions, items within unsafe extern blocks may be marked as safe to use. RFC: rust-lang/rfcs#3484 Tracking issue: rust-lang#123743 ## What is stabilized ### Summary of stabilization We now need extern blocks to be marked as unsafe and items inside can also have safety modifiers (unsafe or safe), by default items with no modifiers are unsafe to offer easy migration without surprising results. ```rust unsafe extern { // sqrt (from libm) may be called with any `f64` pub safe fn sqrt(x: f64) -> f64; // strlen (from libc) requires a valid pointer, // so we mark it as being an unsafe fn pub unsafe fn strlen(p: *const c_char) -> usize; // this function doesn't say safe or unsafe, so it defaults to unsafe pub fn free(p: *mut core::ffi::c_void); pub safe static IMPORTANT_BYTES: [u8; 256]; pub safe static LINES: SyncUnsafeCell<i32>; } ``` ## Tests The relevant tests are in `tests/ui/rust-2024/unsafe-extern-blocks`. ## History - rust-lang#124482 - rust-lang#124455 - rust-lang#125077 - rust-lang#125522 - rust-lang#126738 - rust-lang#126749 - rust-lang#126755 - rust-lang#126757 - rust-lang#126758 - rust-lang#126756 - rust-lang#126973 - rust-lang#127535 - rust-lang/rustfmt#6204 ## Unresolved questions I am not aware of any unresolved questions.

traviscross · 2024-08-04T00:34:32Z

@rustbot labels -S-tracking-ready-to-stabilize +S-tracking-ready-for-edition

With the merge of #127921, this item is now ready for Rust 2024.

Thanks to @spastorino for pushing this important work to completion.

…-style-guide, r=compiler-errors Add unsafe to extern blocks in style guide This goes after this is merged: - rust-lang#127921 r? `@traviscross` Tracking: - rust-lang#123743

…-style-guide, r=compiler-errors Add unsafe to extern blocks in style guide This goes after this is merged: - rust-lang#127921 r? ``@traviscross`` Tracking: - rust-lang#123743

Rollup merge of rust-lang#127922 - spastorino:unsafe-extern-blocks-in-style-guide, r=compiler-errors Add unsafe to extern blocks in style guide This goes after this is merged: - rust-lang#127921 r? ``@traviscross`` Tracking: - rust-lang#123743

…ide, r=compiler-errors Add unsafe to extern blocks in style guide This goes after this is merged: - rust-lang/rust#127921 r? ``@traviscross`` Tracking: - rust-lang/rust#123743

traviscross added C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-lang Relevant to the language team, which will review and decide on the PR/issue. A-edition-2024 Area: The 2024 edition labels Apr 10, 2024

traviscross assigned spastorino Apr 19, 2024

spastorino mentioned this issue Apr 28, 2024

Unsafe extern blocks #124482

Merged

oli-obk added A-edition-2027 Area: The 2027 edition and removed A-edition-2024 Area: The 2024 edition labels Apr 29, 2024

traviscross added F-unsafe_extern_blocks `#![feature(unsafe_extern_blocks)]` B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. labels May 6, 2024

traviscross mentioned this issue May 19, 2024

Unsafe Extern Blocks rust-lang/rfcs#3484

Merged

traviscross added S-tracking-impl-incomplete Status: The implementation is incomplete. S-tracking-needs-migration-lint Status: This item needs a migration lint. S-tracking-needs-documentation Status: Needs documentation. labels May 21, 2024

rustbot added A-edition-2024 Area: The 2024 edition and removed A-edition-2027 Area: The 2027 edition labels Jun 4, 2024

traviscross removed the S-tracking-needs-migration-lint Status: This item needs a migration lint. label Jun 4, 2024

dtolnay mentioned this issue Jun 7, 2024

Parse safe items in extern blocks dtolnay/syn#1675

Open

traviscross removed the S-tracking-impl-incomplete Status: The implementation is incomplete. label Jun 11, 2024

rustbot added the I-style-nominated Nominated for discussion during a style team meeting. label Jun 11, 2024

traviscross added the S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR label Jun 11, 2024

compiler-errors mentioned this issue Jun 20, 2024

Properly gate safe keyword in pre-expansion #126757

Merged

This was referenced Jun 20, 2024

safe keyword is allowed in all function contexts #126749

Closed

safe keyword is not feature-gated #126755

Closed

This comment was marked as resolved.

Sign in to view

traviscross mentioned this issue Jun 25, 2024

Bad replacement for unsafe extern block suggestion #126756

Closed

chenyukang mentioned this issue Jun 26, 2024

Fix bad replacement for unsafe extern block suggestion #126973

Merged

spastorino mentioned this issue Jul 18, 2024

Stabilize unsafe extern blocks (RFC 3484) #127921

Merged

This was referenced Jul 18, 2024

Add unsafe to extern blocks in style guide #127922

Merged

Changes for unsafe extern blocks (RFC 3484) rust-lang/reference#1536

Merged

Stabilize unsafe extern blocks rust-lang/edition-guide#313

Merged

traviscross removed the S-tracking-needs-documentation Status: Needs documentation. label Jul 21, 2024

traviscross closed this as completed Aug 4, 2024

rustbot added S-tracking-ready-for-edition Status: This issue is ready for inclusion in the edition. and removed S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR labels Aug 4, 2024

traviscross removed the I-style-nominated Nominated for discussion during a style team meeting. label Aug 4, 2024

This was referenced Aug 29, 2024

Rust 2024 -- unsafe extern "C" hard req. anderslanglands/bbl-build-rs#5

Closed

Rust 2024 -- unsafe extern "C" hard req. anderslanglands/babble#15

Open

traviscross mentioned this issue Sep 17, 2024

Rust 2024 Edition rust-lang/rust-project-goals#117

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tracking Issue for RFC 3484: Unsafe Extern Blocks #123743

Tracking Issue for RFC 3484: Unsafe Extern Blocks #123743

traviscross commented Apr 10, 2024 •

edited

Loading

oli-obk commented Apr 29, 2024 •

edited

Loading

traviscross commented Jun 4, 2024

traviscross commented Jun 11, 2024

ehuss commented Jun 20, 2024

This comment was marked as resolved.

This comment was marked as resolved.

traviscross commented Aug 4, 2024

Tracking Issue for RFC 3484: Unsafe Extern Blocks #123743

Tracking Issue for RFC 3484: Unsafe Extern Blocks #123743

Comments

traviscross commented Apr 10, 2024 • edited Loading

About tracking issues

Steps

Related

oli-obk commented Apr 29, 2024 • edited Loading

traviscross commented Jun 4, 2024

traviscross commented Jun 11, 2024

ehuss commented Jun 20, 2024

This comment was marked as resolved.

This comment was marked as resolved.

traviscross commented Aug 4, 2024

traviscross commented Apr 10, 2024 •

edited

Loading

oli-obk commented Apr 29, 2024 •

edited

Loading