Re: Groovy 4 compiler seems to leave behind Threads

Am 03.02.22 um 17:27 schrieb Rachel Greenham:
> In other words, don’t worry, it’s not a resource leak. :-) But if you really want to mess with it the javadoc should help, you can set the thread factory via a system property, for instance, as well as monitoring what it’s doing.

OK. If I understand it correctly there's no way to create threads specifically for the Groovy compiler. Descriptive thread names would be helpful when dealing with large thread dumps or logs. But I understand the simplicity argument for using the global thread pool. I think we can deal with it. ;-)

-- 
Alex