Ian Smith

I guess maybe Obj go brrr.... I see a "clean" way there

But this is really annoying because everything ends up tainted by the object system and classes cast internally after checking the sort... it's a mess

I don't want the user to have to implement a variant that handles all of the sorts in one go (e.g. implement this massive join and variant that checks that things line up). Only solution I've come up with is falling back to the object system and having a virtual class that supports my ops

Alright annoying Ocaml design thing I can't solve. A framework I'm dealing with has users define their own terms which compute a variety of sorts (represented as strings). I want to make a library generic over the representation of each sort and additionally fetch a CPO implementation for each