kuilpd wrote: > but I can also imagine doing something like python's "arbitrary width" > integers.
Isn't this basically `llvm::APInt` class? We could just disregard every integer's type, add their values as `APInt` and return the result with a maximum width integer type. I kind of like this path, makes things way simpler. The only thing is that if the values of shorter types are expected to overflow and truncate, we would get a wrong result, and I'm not sure how important this is in the context of data inspection. https://github.com/llvm/llvm-project/pull/147064 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
