Like an option but not optional.
Guarantees external immutability for its contained object.
Increments a number returning "gap" mumbers, numbers that are reported to be no longer "be in use", first.
Removed, look at Accessorise.
Like the standard ControlFlow enum, without the type requirements.
Convert Options into certainty with the get_some declarative macro.
Tait and derive macro used to implement the weak-self design pattern.
Cast stuff into &dyn Any and &mut dyn Any.
The items in this module help you work with RefCells.
Collection related stucts and traits, some of which are inspired by .NET collections.
Panicking made convenient.
Event structs loosely inspired by .NET events.
A Trait and trait implementations for helping you get the value of one for each standard numeric type.
Moved to: IncDec
Reference counting related helpers.
Look at AsStr and AsMutStr, SendableText and related structs moved to Highly Sendable.
Now in the Rc module.
For when you want to do stuff with values and generic type constraints.
Build with the latest stable compiler.
| Feature | Description |
|---|---|
| serde | Enable serde related features. |
| drop_panic | Enable the drop_panic module. |
| macros | Enable the declarative macros. |
- Add more documentation
- Add code examples
- Add more tests
- Clean-up the code
This project uses a coding style the emphasises the use of white space over keeping the line and column counts as low as possible.
So this:
fn foo()
{
bar();
}Not this:
fn foo()
{
bar();
}Licensed under either of:
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0 (see also: https://www.tldrlegal.com/license/apache-license-2-0-apache-2-0))
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT (see also: https://www.tldrlegal.com/license/mit-license))
at your discretion
Please clone the repository and create an issue explaining what feature or features you'd like to add or bug or bugs you'd like to fix and perhaps how you intend to implement these additions or fixes. Try to include details though it doesn't need to be exhaustive and we'll take it from there (dependant on availability).
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.