Jlalond wrote: I can still make an RFC if that is desired, but I believed we reached a compromise with the new broadcast bit. I think we should frame the SBProgress very differently to @labath's recent improvements to Progress itself. I think the critical feature is the disposal of SBProgress and the deconstruction of the progress object. I think it's probably going to be fine if this deconstruction in non deterministic in Python. I can't imagine many workflows that would repeatedly creating Progresses where their lifetimes overlapping would interrupt with each other.
@labath I'll leave final sign off to you in this case. I personally think it's fine to merge as is because the API is so small, and I think we can add new semantics or extend the API if needed. https://github.com/llvm/llvm-project/pull/119052 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
