One of the new features called out in @araq's Nim 2 talk is Task, which bundles 
up an expression for evaluation later (asynchronously by a thread pool, in his 
example.)

There wasn’t a lot of detail in the talk; as far as I could tell, Task is just 
a wrapper for a lambda/closure/proc with no arguments. Which is a useful 
abstraction but does not seem exciting enough to be described in a short 
overview video.

I assume that I missed something and the Task type is cooler than I realize. 
Does someone with more knowledge feel like explaining it?

Reply via email to