Make naming adhere to Rust API guidelines, docs, CLI help, dependencies bump #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make naming adhere to Rust API guidelines.
get_
prefixes were removed where neccessary.AsRef
,TryFrom
orFrom
.SByte
etc. becameSignedByte
etc. since the above API guidelines call forSbyte
otherwise, which is less easy on the eyes.Docs had newlines & missing periods added where necessary and spaces removed. The latter particularly before/after a slash '/').
On that note, I'm about to open a feature suggestion for
rustdoc
to add a hair space (U+200A
) automatically before/after a slash.That has the nice side-effect that the browser will (line) break at the slash without having to add the eyesore that a full space before/after introduces. This is only relevant for long words separated by a slash anyway; i.e. not this crate.
See e.g. the Wikipedia section about em/en-dashes for the same (introducing line breaks w/o adding visible spacing).
Updated/fixed some CLI help/about messages.
Bumped dependencies in
Cargo.toml
(& removed patch version) and bumped crate version to1.6.0
to signal API breakage introduced by this PR.