Improving `memory` with better abstractions

Thank you for putting it into formal language than I can muster!

Yes I did hem and haw about terminology a bit before settling on endo to emphasize the (a -> a) nature of endomap, but it is equally-well captured as a ‘monoid of equivalent / mapped (sub)types or something*’ slash as a category with composition eg EndoMap Bit Byte <> EndoMap Byte Word64 yields EndoMap Bit Word64 and endomap @Bit . endomap @Byte . endomap @Word64. Some famous quote about monoids in the category of endofunctors comes to mind about these things being related? We could also have described endomap in terms of over each using Each from lens.

• As I so would have tried to put it, which I know is Not a Well-Formed-Enough Statement, so again, thank you for putting it better than I would have

I have been also considering the less loaded terms of EndoMap, EndoFold, EndoTraverse eg minus the Functor/able and just named after the primary function.