Okay, so. Yesterday, I was trying to describe what I felt would fit with my understanding of literate programming, and today, I realized that what I was describing is basically what rustdoc does. Regardless, let's see if it looks good if I try to impose a narrative on Structured Data's documentation.
So, here's where that ended up:
- Wrote up explanations of roughly how to use the adt and match modules.
- Doctest in the adt module.
- Turns out Divide and Cover can't handle doctests.
- Frantic merges.
- Sedate Travis jobs.
I think I'll need to try again later to improve the match-related documentation, because that offers somewhat more elaborate capabilities than adt does.
I'd also like to give the match module its own doctest, but I'd like to give Travis a chance to catch up.
I definitely want to give this another try, because I ended up getting kind of distracted after my initial shot at improving the documentation.