I've never had a chromebook which didn't make my fingers hurt. Ditto macbooks though, so that comparison is basically worthless to me :D I guess that they might be better than a mac, but I've never used either long enough to know if the how the levels of pain and horror relate.
Nowadays it's a text entry field, but it doesn't auto-full-hilite when you press it, so you still have to tap it, tap it again to give it focus, backspace it to empty it, and then type in the distance.
Data entry is hard.
Worst spinner thing I ever had was a data entry thing for rowing distance in the Garmin app - It had two spinners, one for meters, and one for 10ths of a meter. I literall had to scroll from 1.0 to 1500.0 on a regular basis.
Reiterating what others seem to already have said -- `unimplemented!()` is your friend, as is `.unwrap()`. I find I write the code faster if I write the documentation **first** because that way I already know how I want it to work before I write it.
Oh indeed it's not always possible to; but if the AST is designed to represent Markdown rather than the generic form that Pandoc's AST takes, it ought to be *more* possible.