This is the dumbest possible "mergestate" implementation: it doesn't actually
handle conflict storage in the slightest, but for the current in-memory merge
cases it works great, and prevents us from accidentally touching .hg/merge
while doing non-wdir operations.
NOT DONE: this breaks tests in future changes in the series, currently getting
stuck on the "premerge()" method in the mergestate object.
Can we really get the merge driver to work with memmergestate? Maybe it's better to make memmergestate.mergedriver raise an exception so we catch it?
Ah, I was curious how that could possibly work so far and it turns out that there is indeed a check at merge.py:2039. You could move that exception to memmergestate.mergedriver, I think.