-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
remove standard library information from the Rust manual #11794
Comments
Generally agree with this, though I think the language's interface to the library (intrinsics, lang items, possibly built-in syntax extensions) is in scope, but non-normative (unstable). |
I don't know what parts of std are described in the manual, having not read it in a long time. |
@brson: I opened this based on it describing the runtime's memory allocation as using I think it would be a good idea to cover intrinsics and lang items there too. However, we can probably get rid of the built-in syntax extensions as a language feature now that they can be dynamically loaded. It might need some tweaking to make it an invisible change to users of the standard library. |
We now say
We do still mention I'd love some clarity here. |
Fixes rust-lang#11794 I mostly removed superflous examples which use the standard library. I have one more quesiton here though: threads. They're mostly a library thing, at this point, right?
I think this should be a language specification, and should avoid describing the library. The language semantics and grammar are a much saner scope to cover than the entire standard library. Implementation details like the standard library's choice of allocator are even more out of place.
The text was updated successfully, but these errors were encountered: