I ran into something similar, but forgot to report it. I think your idea is good, and should be added.
On Fri, Dec 26, 2025, 6:01 AM Kasper Nielsen <[email protected]> wrote: > Hi, > > I encountered a WrongThreadException the other day from invalid use of > StructuredTaskScope. However, finding out why was a bit more difficult > than needed. I had to fire up a debugger to get the owning thread of > my StructuredTaskScope. It would have been somewhat easier to figure > out what exactly went wrong if StructuredTaskScopeImpl.ensureOwner > included the name of both the owning thread, and the current thread in > its error message. > > /Kasper > >
