https://github.com/magnet/metered-rs

Maybe relevant to #3.

I just skimmed through the docs, so bear with me:

I have two functions, one is cached, and another one might invalidate the cache or some key in it. There's no example of how to get ahold of the cache in the second function, in order to be able to call methods like cache_remove or cache_clear.

The second function is not cached, it just invalidates the cache, and there can be an infinite

We keep messing up the Markdown documentation files. To avoid that, we should add markdownlint to the Travis build script.

It's bad UI design to have required option flags on a command-line tool. In fact, the documentation for Python's in-stdlib argument parsing library explicitly teaches people to avoid it.

This...

rustig [FLAGS] [OPTIONS] --binary <FILE>

...should be this...

rustig [FLAGS] [OPTIONS] <FILE>

Requiring --binary or -b before what could be a positional argument just makes the c

the documentation includes a the following suggested way to run this container

docker run --rm \
    -v ${PWD}:/code \
    -v ${HOME}/.cargo/registry:/root/.cargo/registry \
    -v ${HOME}/.cargo/git:/root/.cargo/git \
    softprops/lambda-rust

this is actually what the [serverless-rust](https://github.com/softprops/serverless-rust/blob/36615f4ec9b887f73dba27c02abf0efa179090c6/

Following points need to be covered:

• Options and Results
• ? operator
• Error handling
• File handling
• Path and PathBuf types
• Parsing String and &str
• Bit manipulation and 16-bit RGB565 representation
• vec vs arrays, and the clone trait. Objects allocated on the heap vs stack.

Please feel free to add your answers below, I will start to curate them sometime next week and will