Well yeah, Seph is right as usual I’ve been updating my MLIR generation code to use Twine lately: https://llvm.org/doxygen/classllvm_1_1Twine.html#details https

Well yeah, Seph is right as usual I’ve been updating my MLIR generation code to use Twine lately: https://llvm.org/doxygen/classllvm_1_1Twine.html#details https://llvm.org/doxygen/classllvm_1_1Twine.html#details LLVM has been using rope data structures for some time. There is more discussion about it here: https://lists.llvm.org/pipermail/llvm-dev/2011-July/041639.html https://lists.llvm.org/pipermail/llvm-dev/2011-July/041639.h... In my situation when parsing lines of code Twine stores the file path and concats the line number and column when getting the location within a file. It does this a lot so using Twine there really helps. The rope data structure can be used in a number of ways.