`ThreadLocal` stores a separate value per thread (often used for request context). The common pitfall is thread pools: threads are reused, so values can “leak” between requests unless you clear them (`remove()` in a `finally`).
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "what-does-`threadlocal`-do-and-what-is-a-common-"
function explain() {
// Start from the core idea:
// `ThreadLocal` stores a separate value per thread (often used for request context). The com
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).