Skip to content

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

Merged
merged 6 commits into from
May 5, 2017
Merged

Libz blitz #164

merged 6 commits into from
May 5, 2017

Conversation

brson
Copy link
Contributor

@brson brson commented May 4, 2017

No merge.

cc @aturon @dtolnay @rust-lang/libs

"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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/documentating/documenting

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol

@aturon
Copy link
Member

aturon commented May 4, 2017

cc @rust-lang/core


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
Copy link
Member

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?

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

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/?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Thanks.

Copy link
Member

@steveklabnik steveklabnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great!

broader community will also apply this process completely independently to
crates the libs team won't have time to discuss.

### How to help
Copy link
Member

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.

### 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
Copy link
Member

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.

@brson brson merged commit 5e6f946 into rust-lang:gh-pages May 5, 2017
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

Successfully merging this pull request may close these issues.

6 participants