concept thread pool in category clojure

This is an excerpt from Manning's book Clojure: The Essential Reference.
These threads are often kept alive in a thread pool and with them, the function objects they ran. The function object, in turns, could be holding a reference to arbitrarily large data, even if the function already returned its results.
fn*ensures that the references the function hold are set tonilatfer the result returns. This is also an important feature to have when writing macros that delegate to wrapping functions, quite a common idiomatic pattern, in order to avoid retaining memory for longer that is actually needed.
The reason why
futurebenefits from once-only semantic is because after running the body expression thefutureobject can stay around for arbitrarily long time (even when terminated). The once-only semantic gives the garbage collector an opportunity to remove potentially large locals even when afutureis still referenced by a thread pool (a common scenario). If you decide to usefuture-calldirectly, it is advisable you use the once-only semantic to avoid potential out of memory issues.