Matthew Butterick

> Has there been effforts or thoughts on creating canonical links in a similar vein as the first example with pollen? No, because this* is a form of magic performed...

I wouldn’t dissuade anyone from experimenting. Consider, however, that the pagetree also cooperates with `raco pollen render ···` to render certain files on disk. For that reason, it usually makes...

The problem seems to be in the [signature](https://github.com/lexi-lambda/racket-collections/blob/master/collections-lib/data/collection/indexable.rkt#L13) of the `ref` generic: ``` (ref indexable . _) ``` This notation means that the implementation of `ref` must have one fixed...

The `define-generics` docs don’t mention it, but I accidentally discovered how to notate optional arguments in the generic signature: `(ref indexable idx [failure-thunk])`

> my original intention was to make such support optional but allowed I’m a generics noob. I have no opinion. Just observing that the docs are incomplete. So maybe what...

Yes: accept the arguments in either order. Unlike `take` in `racket/base`, yours insists on one `exact-nonnegative-integer?` and one `sequence?`, so there is no possible ambiguity

Another approach, also backward-compatible: publish the consistent API under a different collection name.

PS `Z` works fine.

I suppose I was hoping that `~t` and `parse-moment` would turn out to be true inverse functions, in the sense that a moment string returned by `~t` could always be...

The CLDR rules seem to acknowledge the many ambiguities and then [punt entirely](http://unicode.org/reports/tr35/tr35-dates.html#Parsing_Dates_Times) on specifics: when parsing, it can be “especially complicated … to figure out what the user meant.”...