Hello, In #1401 <https://github.com/apache/logging-log4j2/pull/1401> against the `main` branch, I am working on moving JSON Template Layout's "recycler" concept to `log4j-core` and replacing all `ThreadLocal` usage with that. We want to know if there are opportunities to take advantage of scoped values (SVs), which will be introduced with JEP 429, and if so, accommodate them in the recycler abstraction.
In its current form, the recycler is designed to offer [reusable] object pooling to facilitate garbage-free logging. Log4j components (appenders, layouts, etc.) will work against the recycler API and users will either choose one of the provided implementations (no-op, concurrent queue, queue in a `ThreadLocal`) or provide theirs. I am not able to see how SVs would help us with object pooling and, hence, the recycler API. I would appreciate some feedback on this. Kind regards.
