<!-- Thank you for taking the time to report an issue! We're glad to have you involved with Ruff. If you're filing a bug report, please consider including the following information: * List of keywords you searched for before creating this issue. Write them down here so that others can find this issue more easily and help provide feedback. e.g. "RUF001", "unused variable", "Jupyter notebook" * A minimal code snippet that reproduces the bug. * The command you invoked (e.g., `ruff /path/to/file.py --fix`), ideally including the `--isolated` flag. * The current Ruff settings (any relevant sections from your `pyproject.toml`). * The current Ruff version (`ruff --version`). --> After running RUF005 in https://github.com/mhammond/pywin32/pull/2230 , I was left with some nested unpacking  I feel like the following case should be detectable and flagged: ```python # from foo(*{bar}) foo(*[bar]) foo(*(bar,)) foo(*[bar, *bar2]) foo(*(bar, *bar2)) foo(*[*bar2, bar]) foo(*(*bar2, bar)) # to foo(bar) # Not a safe fix from *{bar} foo(bar) foo(bar) foo(bar, *bar2) foo(bar, *bar2) foo(*bar2, bar) foo(*bar2, bar) ``` (same with assignments and possibly more cases I haven't thought of) Edit: Removed sets since https://github.com/astral-sh/ruff/issues/10592#issuecomment-2785004944 > Elements may be deduplicated and sets are unordered