jimingham wrote: > I don't consider it a failure to not be able to perform mixed language > expressions. But it would have to be presented to the user in a way that is > understandable, which could be a challenge. > > Anyway, I pushed the change that scopes the lookup to the expected language. > > thank you for the reviews
I'm not sure what you mean by "mixed language expressions". What I'm trying to avoid is, if stopped in a swift frame, you get: (lldb) p cpp_object_ptr <get a value> (lldb) p cpp_object_ptr->cpp_method() <unknown identifier cpp_object_ptr> That's not a cross language expression, that's a perfectly good C++ expression. I don't think it makes sense to present simple variables of all language types, but not evaluate expressions using all the available expression parsers, starting with the obvious one first. https://github.com/llvm/llvm-project/pull/85152 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
