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.

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

add explanation next to #[cfg(TODO)]s in code #137

Open
Lotterleben opened this issue Jan 29, 2021 · 2 comments
Open

add explanation next to #[cfg(TODO)]s in code #137

Lotterleben opened this issue Jan 29, 2021 · 2 comments

Comments

@Lotterleben
Copy link
Contributor

so that participants wondering why they can't instantiate a thing get a hint right where the problem is (I think it's mentioned in the book already)

@japaric
Copy link
Contributor

japaric commented Feb 2, 2021

I think it may be best to use block comments (/* .. */) which is more familiar to C and non-Rust programmers.

@Lotterleben
Copy link
Contributor Author

Agreed. maybe we can sneak in a "🔎 in Rust projects, you may encounter another block comment notation: #[cfg(TODO)] effectively comments out the following element, which could be anything from a struct member to a module" in the materials?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants