Your example above is maybe a good example why we do want range deletes, among other operations. In my view the problem is matching the semantics of the CRDT li

Your example above is maybe a good example why we do want range deletes, among other operations. In my view the problem is matching the semantics of the CRDT library to the semantics of the problem domain. Having more options always makes this easier (but not for the maker of the CRDT library :-p). I would even think that maybe we need CRDTs with programmable semantics along side inserts, deletes, move, range delete, etc (just an idea). I would love to work on a structural editor for a programming language. Maybe I will start some experiments after my current project. Keep up the good work!