Hello! Yes your understanding is correct. However it is worth noting that when MapNode was originally implemented it was meant to remove some boilerplate from Project and Filter, as previously these nodes spawned separate tasks. As we move towards more efficiently using pipeline execution, this boiler plate can go away, and MapNode with it. I have a series of pull requests in flight that removes MapNode. I’d suggest for any new code to avoid using it.
Sasha > 19 мая 2022 г., в 07:38, Li Jin <ice.xell...@gmail.com> написал(а): >
