Three Dollar Quill

I'm feeling better now. More focused. Let's not squander it.

I tried out those renames I was thinking of for MOTR, and I think that they did improve things. To be sure, I'm going to need to step away from the code for a bit, then read over the modules I changed to see if they're any clearer.

After getting those changes in, I find myself focusing on a helper function that I wrote into Axes.combine. That function clearly needs to go together with the whole... "functions only defined on finite sets" concept that ties a lot of the new layers of MOTR together. To me, that means that the relevant module needs to be moved higher in the tree, next to the saltate module. And that suggests that I should try to come up with a non-awkward name for it.

per_item_parametric_mapping to... Hm. Basically, the idea is that this type represents the same concept as a parametrically typed function, but it's only defined for values that are specifically set.

Not without convincing it doesn't.

Anyway, what to call this... After the renames I've done, shortening it to ParametricMapping doesn't sound unreasonable to me. Need to figure out the right naming conventions around the magmas, though. The annoying thing about ParamatricMapping, when I think about it, is that you need to look at it and think "Well, Mapping is already parametric, so how is this different?"

Well, I'll take some time to think about this, and see what I feel like doing.

Good night.