-
Notifications
You must be signed in to change notification settings - Fork 303
Libz blitz #164
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
Libz blitz #164
Conversation
_posts/2017-05-05-libz-blitz.md
Outdated
"use ownership to encapsulate invariants"; consistent naming conventions like | ||
`mut`, `ref`, `as`, `into`, that let users intuit what they don't know | ||
from what they do; small details of presentation that add up, like consistently | ||
documentating possible error cases in a dedicated "Errors" section; and so many |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/documentating/documenting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol
cc @rust-lang/core |
_posts/2017-05-05-libz-blitz.md
Outdated
|
||
Because of Cargo, we can "include batteries" without literally putting them into | ||
the standard library; pulling in other crates is nearly as easy as using the | ||
standard library (and will get even easier this year). But to capitalize on this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, is "will get even easier this year" referring to something in particular?
_posts/2017-05-05-libz-blitz.md
Outdated
evaluation grow in scope, presumably the tasks that arise will grow as well. | ||
|
||
[`byteorder`]: https://docs.rs/byteorder | ||
[`bitflags`]: https://doc.rust-lang.org/tempdir/tempdir/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this point to https://docs.rs/bitflags/?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great!
_posts/2017-05-05-libz-blitz.md
Outdated
broader community will also apply this process completely independently to | ||
crates the libs team won't have time to discuss. | ||
|
||
### How to help |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe consider phrasing this as a question, given the first sentence.
_posts/2017-05-05-libz-blitz.md
Outdated
### Rust standards of community | ||
|
||
We have some idea of what goes into publishing exceptional Rust crates, but the | ||
Rust library team is not the sole authority of Rust API design — the Rust crate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Em dash should be used without spaces.
No merge.
cc @aturon @dtolnay @rust-lang/libs