@ericniebler My gut feeling is that I agree with your intention, as cannot think of any weird type that does that, but formally defining what "specified moved-from state" means might be tricky and conflict with legitimate use cases.
@MarkCallaghanDB If you don't cite the prior art in other areas you're silently implying you're the first one to come up with the idea, instead of sharing credit.
@MarkCallaghanDB My comment was just pointing to prior art, hence the "for example", I didn't say "use folly".
And novelty is definitely a factor when evaluating a paper, especially if it doesn't have a thorough review of related work. But this was a workshop paper, so the bar is likely lower.
@triketora The empiricists get stuck on trivial problems (or introduce trivial bugs) that could be solved by spending 5 minutes reading the definition.
The formalists get stuck in endless nitpicking about the correct definitions.
The former are usually more productive.
@triketora Oversimplifying things a lot, I think that there are two camps in programming, the empiricists (try and see what happens) and the formalists (strictly derive from the definitions). Each camp finds the way the other operates incomprehensible and infuriating.
@MarkCallaghanDB Also the idea of using a pool of memory that is never returned to the OS so it can be used by concurrent algorithms that use version numbers to detect validity is not new, see for example IndexedMemPool in folly and its uses.
@MarkCallaghanDB The analysis and experiments are based on a flawed understanding of hazard pointers, readers don’t need sequentially consistent writes, a compiler barrier is enough (with a membarrier on reclamation), so their overhead is off by an order of magnitude.