Skip to content

Tracking issue for making std-surfaced macro intrinsics available via std:: paths #57289

New issue

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

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

Already on GitHub? # to your account

Closed
mark-i-m opened this issue Jan 2, 2019 · 2 comments
Labels
A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-resolve Area: Name/path resolution done by `rustc_resolve` specifically C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team

Comments

@mark-i-m
Copy link
Member

mark-i-m commented Jan 2, 2019

Quoting @cramertj in #53128 (comment)

@mark-i-m Are you referring to how std-surfaced macro intrinsics aren't yet usable by their std paths? e.g. This code only works if you remove std:::

fn main() {
    println!("{}", std::format_args!("{}", 5));
}
error[E0433]: failed to resolve: could not find `format_args` in `std`
 --> src/main.rs:2:25
  |
2 |     println!("{}", std::format_args!("{}", 5));
  |                         ^^^^^^^^^^^ could not find `format_args` in `std`

error: aborting due to previous error
@cramertj
Copy link
Member

cramertj commented Jan 2, 2019

cc @eddyb, @petrochenkov

@Centril Centril added T-lang Relevant to the language team C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC labels Jan 2, 2019
@Centril Centril changed the title [tracking issue] Make std-surfaced macro intrinsics available via std:: paths Tracking issue for making std-surfaced macro intrinsics available via std:: paths Jan 13, 2019
@jonas-schievink jonas-schievink added A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-resolve Area: Name/path resolution done by `rustc_resolve` specifically labels Nov 26, 2019
@scottmcm
Copy link
Member

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-resolve Area: Name/path resolution done by `rustc_resolve` specifically C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team
Projects
None yet
Development

No branches or pull requests

5 participants