bnbarham wrote: > Isn't that a better way to support the expression parsing logic where we > execute statements on the global scope to evaluate their results?
This is currently enabled during module loading, where we definitely don't want any change in behavior IMO. Perhaps we could enable it after? If we think this is useful to keep I'll need to look into how https://github.com/llvm/llvm-project/pull/65683 broke LLDB testing: ``` lldb-api.commands/expression/diagnostics.TestExprDiagnostics.py lldb-api.lang/objc/modules.TestObjCModules.py lldb-api.lang/objc/modules-incomplete.TestIncompleteModules.py lldb-api.lang/objc/modules-non-objc-target.TestObjCModulesNonObjCTarget.py lldb-api.lang/objc/modules-objc-property.TestModulesObjCProperty.py ``` That change should effectively be NFC as far as `-fincremental-extensions` is concerned, so if you have any ideas that would be appreciated :) https://github.com/llvm/llvm-project/pull/66271 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
