std::convert::TryFrom has an associated type called Error and std::str::FromStr has an associated type called Err 🦀oops🦀

hmm, i have both a binary and library target in this crate, and cargo runs all the tests for each target, so it runs the tests twice can’t see if there’s a cfg attribute for targets so i can disable them in the source tho i can turn off the lib tests in cargo.toml

grump, bah, since when was this required, and where is this % thing documented? $ rustdoc doc/spec.md error: invalid markdown file: no initial lines starting with `# ` or `%`

while learning Rust i find i keep oscillating between hmm i should have a type for these values (lots of impl this and impl that) wow this is fiddly and annoying (delete lots of code)

well, after digging my way out of a rather heavy refactoring, I think my current project for learning Rust is working OK github.com/fanf2/leapsecs

next task is to learn rustdoc i tend to write docs when a project is reasonably settled and at the polishing stage; often the documentation tells me that my API or UI could do with improvements 🤪

i drew the leap second clock when i was procrastinating about writing the functions that output the leap second list in my compact binary format

Oh and I should also get a fuzzer working, because there are too many parsers and serializers in this code (cargo fuzz? anything else worth trying?)

so rustdoc is nice and straightforward main Q i have is how to document trait implementations the most important functionality in my crate is in things like `impl FromStr` and `impl Display` i’ve explained this in the module docs since that seemed like the best place

i keep wanting ternary ?: in my rust because a full-fat if-else is so bulky