Remove build via Debian's official Rust compiler
Add build manifests
Initial commit
This is a collection of code I use in many/most of my Rust projects.
All source code is licensed under the terms of the MPL 2.0 license.
Simply run cargo test
, with whatever feature set you wish to use.
Or with cargo-hack:
cargo hack --each-feature test
.
Unless I get requests to do so, I do not intend to list this on the crates.io
registry. Add to your Cargo.toml
:
[dependencies]
utility_belt = {git = "https://git.sr.ht/~rjframe/utility_belt_rs", tag = "v0.1.0"}
Note: crates.io will not let you publish a package that includes a git dependency. If you intend to use this library and publish your package, let me know and I'll list this on the registry.
The Cargo.toml
provides a complete list of dependencies for any given feature.
Alternatively, most files are either wholly or mostly-independent, and can
simply be copied into your project source, with minimal dependency updates to
your Cargo.toml
and module paths (useful if all you want is, e.g., the Uniq
iterator). The MPL applies at the file boundary, so you can safely copy these
files as-is without worrying about messing up the licensing for your own code.
Build and run the documentation (cargo doc --all-features --no-deps --open
)
for full documentation. This section is a brief review of the code:
The official code repository is hosted at https://git.sr.ht/~rjframe/utility_belt_rs; please send any bug reports, patches, or other communications to https://lists.sr.ht/~rjframe/public.
The first line of a commit message should summarize the purpose of the commit. It should be a full sentence but end without a period. The subject line must be no more than 72 columns, preferably no more than 50.
If the commit addresses a specific feature or module, prefix the commit message with that name (e.g., "iter: Some message here").
Write the subject in imperative style (like you're telling someone what to do); use "Add xyz" instead of "Added xyz", "Fix" instead of "Fixed", etc.
The body of the message must have a hard 72-column line limit.