Skip to content

Stabilize proc_macro_value feature#151973

Open
GuillaumeGomez wants to merge 1 commit into
rust-lang:mainfrom
GuillaumeGomez:stabilize-proc_macro_value
Open

Stabilize proc_macro_value feature#151973
GuillaumeGomez wants to merge 1 commit into
rust-lang:mainfrom
GuillaumeGomez:stabilize-proc_macro_value

Conversation

@GuillaumeGomez

Copy link
Copy Markdown
Member

Fixes #136652.

The feature implementation is complete: all string related values now have their _value method and proc_macro2 integration seems to be working as expected.

Integers are voluntarily left untouched as an equivalent API for them is much trickier to provide. I'll open an ACP once I come up with a design I'm happy with.

r? @Amanieu

@GuillaumeGomez GuillaumeGomez added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label Feb 2, 2026
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 2, 2026
@jhpratt jhpratt added the needs-fcp This change is insta-stable, or significant enough to need a team FCP to proceed. label Feb 2, 2026
@Amanieu

Amanieu commented Mar 28, 2026

Copy link
Copy Markdown
Member

r? @dtolnay

@rustbot rustbot assigned dtolnay and unassigned Amanieu Mar 28, 2026
@Amanieu

Amanieu commented Mar 28, 2026

Copy link
Copy Markdown
Member

I'm not sure if we should be stabilizing this without at least a sketch for the the integer value API, but I'm not the best person to determine this since I haven't used the proc macro API much.

Comment thread library/proc_macro/src/lib.rs Outdated
Comment on lines +67 to 69
#[stable(feature = "proc_macro_value", since = "CURRENT_RUSTC_VERSION")]
#[derive(Debug, PartialEq, Eq)]
pub enum ConversionErrorKind {

@traviscross traviscross May 31, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to make this non_exhaustive before stabilizing it?

View changes since the review

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this one, not sure if it'll ever need to be updated though.

Comment thread library/proc_macro/src/lib.rs Outdated
@rust-bors

This comment has been minimized.

jhpratt added a commit to jhpratt/rust that referenced this pull request Jun 9, 2026
…e, r=traviscross,Mark-Simulacrum

Make `Literal::byte_character_value` work with bytes as well

As noted in [this comment](rust-lang#151973 (comment)), `byte_character_value` should work for bytes, so this PR fixes it.

r? @traviscross
jhpratt added a commit to jhpratt/rust that referenced this pull request Jun 9, 2026
…e, r=traviscross,Mark-Simulacrum

Make `Literal::byte_character_value` work with bytes as well

As noted in [this comment](rust-lang#151973 (comment)), `byte_character_value` should work for bytes, so this PR fixes it.

r? @traviscross
rust-timer added a commit that referenced this pull request Jun 10, 2026
Rollup merge of #157338 - GuillaumeGomez:byte_character_value, r=traviscross,Mark-Simulacrum

Make `Literal::byte_character_value` work with bytes as well

As noted in [this comment](#151973 (comment)), `byte_character_value` should work for bytes, so this PR fixes it.

r? @traviscross
pull Bot pushed a commit to Kokoro2336/rust-analyzer that referenced this pull request Jun 11, 2026
…iscross,Mark-Simulacrum

Make `Literal::byte_character_value` work with bytes as well

As noted in [this comment](rust-lang/rust#151973 (comment)), `byte_character_value` should work for bytes, so this PR fixes it.

r? @traviscross
@GuillaumeGomez GuillaumeGomez force-pushed the stabilize-proc_macro_value branch from d96083f to 300da0f Compare June 15, 2026 13:39
@rustbot

rustbot commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@GuillaumeGomez

Copy link
Copy Markdown
Member Author

Fixed merge conflict. Are there any concerns remaining or should we start an FCP?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-fcp This change is insta-stable, or significant enough to need a team FCP to proceed. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tracking issue for proc_macro_value

6 participants