Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

treat intrinsics as native functions in the documentation #10725

Closed
thestinger opened this issue Nov 29, 2013 · 2 comments
Closed

treat intrinsics as native functions in the documentation #10725

thestinger opened this issue Nov 29, 2013 · 2 comments
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@thestinger
Copy link
Contributor

Intrinsics use the Rust ABI, so there is no difference from an external point of view.
This was referenced Feb 28, 2014
Closed
Closed
@brson
Copy link
Contributor

brson commented Feb 28, 2014

This depends on #12633.

@emberian
Copy link
Member

This is fixed.

flip1995 pushed a commit to flip1995/rust that referenced this issue May 20, 2023
@bors
Auto merge of rust-lang#10725 - y21:issue9914, r=Jarcho
815a07e 
don't remove `dbg!` in arbitrary expressions

Fixes rust-lang#9914

The `dbg_macro` lint replaces empty `dbg!` invocations with the empty string in its suggestion, which is not always valid code in certain contexts (e.g. `let _ = dbg!();` becomes `let _ = ;`). This PR changes it to `()`, which should always be valid where `dbg!()` is valid (`dbg!()` with no arguments evaluates to `()`).

It also special-cases "standalone" `dbg!();` expression statements, where it will suggest removing the whole statement entirely like it did before.

changelog: [`dbg_macro`]: don't remove `dbg!()` in arbitrary expressions as it sometimes results in syntax errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brson @emberian @thestinger