-
Notifications
You must be signed in to change notification settings - Fork 112
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
Conventions around no_std #23
Comments
Including what the |
I'd prefer Alternatively use |
I strongly prefer It aligns better with the optional dependency / implicit feature mechanism. If you have an optional dependency on |
Ah, good point, I completely forgot about that. Bit OT idea: provide a way to create documentation for features? e.g.
Maybe with default doc string for implicit features? That would seem to me like the best of both worlds. |
I've generally gone with "std" for my own projects, however I've seen a decent amount of "use_std" |
Added in a15e953. |
I guess I'll have to rewrite some stuff but I agree with the decision. |
No description provided.
The text was updated successfully, but these errors were encountered: