[Lldb-commits] [lldb] [lldb/script] Migrate ParsedCommand & raw commands onto ScriptedPythonInterface (PR #210430)

[Med Ismail Bennani via lldb-commits]

medismailben wrote:

> Since the template for this ScriptedCommand is new, I don't think we would cause incompatibility by removing the debugger argument from the `__call__` method. I think Alex is right that that's confusing, since it makes you wonder how the debugger you got in `__call__` could be different from the one you got in `__init__`?
> 
> The template really ought to set the debugger passed into `__init__` to `self.debugger` and then it will be clear that's what you use if you want to access the debugger.

This would be tricky in the C++ side: although we can call methods with different arity by just dropping the last arguments, here it's more complicated because we would need to prepend the debugger argument just for this specific method. Since we don't pass the methods using `kwargs` calling convention, order matters. 

https://github.com/llvm/llvm-project/pull/210430