vogelsgesang wrote:

> except that it is a little odd to have a function called 
> NotifyThreadsOfChangedFrameProviders... that does more than notify, it also 
> clears the cached providers. A function called NotifyWhatever should just 
> notify.

LLM-generated proposal:
* InvalidateThreadFrameProviders() — "invalidate" implies clearing cache and 
forcing reload
* RefreshThreadsForChangedFrameProviders() — "refresh" implies clearing and 
reloading
* ReloadThreadFrameProviders() — "reload" implies clearing and reloading

Any preference? Otherwise, I would probably go with 
`InvalidateThreadFrameProviders`

https://github.com/llvm/llvm-project/pull/171482
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to