MixT
MixT copied to clipboard
mpmilano
Prototype Mixed-consistency transaction implementation
Right now we're directly putting the macro-expanded code in the class, which is insufficient dogfood!
The current parser kinda ignores operation associativity. It shouldn't do that. Actual inspect the operator we're parsing to decide associativity correctly.
add read witnesses to compiler, alongside detection of whether they are necessary.
Which ignores whether the clock is up-to-date and always chooses tracking transactions. Currently enabled by a hack in my working copy.
Too many arguments that are just there for overloading resolution and the user needs to supply every time.
it's kinda annoying to find right now
only makes sense to require it for trackable, causal items.
Interface for raw SQL commands as operations. Handles can be dummies except those required by tracking.