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

Properly document compile_error!() #46171

Closed
Havvy opened this issue Nov 21, 2017 · 0 comments
Closed

Properly document compile_error!() #46171

Havvy opened this issue Nov 21, 2017 · 0 comments
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools P-medium Medium priority

Comments

@Havvy
Copy link
Contributor

Havvy commented Nov 21, 2017

https://doc.rust-lang.org/std/macro.compile_error.html

Currently says "Unconditionally causes compilation to fail with the given error message when encountered." and links to the RFC that proposed it. No examples, or otherwise explaining how it's supposed to be used.
@steveklabnik steveklabnik added P-medium Medium priority A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools labels Nov 21, 2017
@Havvy Havvy mentioned this issue Dec 5, 2017
Merged
frewsxcv added a commit to frewsxcv/rust that referenced this issue Dec 6, 2017
@frewsxcv
Rollup merge of rust-lang#46512 - Havvy:doc-compile_fail, r=kennytm
bb239e2 
Give compile_error macro examples

I cannot get Rust to build at all with it complaining about GCC not being a valid C compiler or something, so letting TravisCI be my tester...

Fixes rust-lang#46171
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools P-medium Medium priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@steveklabnik @Havvy