llvm-project.git/lldb/source/API/SBProgress.cpp, branch users/nico/python-2

[LLDB][SBProgress] Add a finalize method (#128966)

2025-03-03T22:01:29+00:00

This patch adds a finalize method which destroys the underlying RAII
SBProgress. My primary motivation for this is so I can write better
tests that are non-flaky, but after discussing with @clayborg in my DAP
message improvement patch (#124648) this is probably an essential API
despite that I originally argued it wasn't.

[LLDB][SBProgress] Fix bad optional in sbprogress (#128971)

2025-02-27T19:08:20+00:00

This fixes the obvious, but untested case of sending None/Null to
SBProgress.

[lldb] Make SBProgress move-only (#124843)

2025-01-28T22:03:17+00:00

I wanted to clarify the semantics around SBProgress. Given the nature of
Progress events, copying seems like the wrong idea. Making SBProgress
move-only (like SBStream) seems like the better choice here.

[LLDB] Add SBProgress so Python scripts can also report progress (#119052)

2025-01-17T20:00:31+00:00

Recently I've been working on a lot of internal Python tooling, and in
certain cases I want to report async to the script over DAP. Progress.h
already handles this, so I've exposed Progress via the SB API so Python
scripts can also update progress objects.

I actually have no idea how to test this, so I just wrote a [toy command
to test
it](https://gist.github.com/Jlalond/48d85e75a91f7a137e3142e6a13d0947)


![image](https://github.com/user-attachments/assets/7317cbb8-9145-4fdb-bacf-9864bf50c467)

I also copied the first section of the extensive Progress.h class
documentation to the docstrings.