It seems we have both a gif encoder and a dxt encoder, but none of them are implemented in save_buffer. I assume this is just an oversight, but it would be nice to fix.

See also #676

If you go here and then scroll down to "HList Codecs," you'll see two examples for making a Codec using ::. The second example contains a :: HNil in the type of threeInts, but codec made similarly in the first example above does not. This causes the first example to not compile - that line should be: `val codec: Codec[

The official Nilearn API/reference documentation at
http://nilearn.github.io/modules/reference.html

seems not to follow a consistent pattern:

• In some cases, some files suffer from a glitch that prevents the variable names and their types being rendered with a blank space and/or a colon in between that would greatly improve the readability, e.g. http://nilearn.github.io/modules/generated/n

I've read the notes for embedded developers:

Unused parts may be pruned by some simple editing of src/libFLAC/Makefile.am

It's not clear to me how to remove the metadata interface. I tried commenting some source files and then running automake:

	#metadata_iterators.c \
	#metadata_object.c \

When I build I get linker errors. Linux calls that I don't want/need as I am runnin

The toml crate has a trick for this. Their serialize_struct recognises their built-in datetime type by name, and delegates to a specialised serializer:
https://github.com/alexcrichton/toml-rs/blob/c1a369f44762045e65989caa9491e153d1f358e6/src/ser.rs#L949-L952

Likewise to deserialize:
https://github.com/alexcrichton/toml-rs/blob/c1a369f44762045e65989caa9491e153d1f358e6/src/de.rs#L582-L589

I ran Jazzy locally on Serpent, and it looks like the documentation percentage is not very high. This is about documentation for functions that the users don't actually access, but still, for completeness and quality, we should document those too.

This looks like it could be a very useful library for my use case, but the two very short examples provided give no insight into how I can use the module to extract functions from a .wasm file. Could you provide some kind of documentation for the module's methods, classes and class methods, etc. along with more comprehensive examples, so that we don't have to sift through the source code to figure

The website seems to reflect API changes in 0.6 but no tag exists. Is 0.6 still in progress or is the release tag missing?