Why compose team are using somethings like `fastFo...
# compose
m
Why compose team are using somethings like
fastForEach
in compose, is it because of the boxing and unboxing ? Also I realized that looping throw the indices and getting each element by index is a lot faster than looping throw elements directly specially when I'm drawing a lot of objects so fast in canvas.
a
It’s documented.
This does not allocate an iterator like
Iterable.forEach
.
👍 1
j
It's also named terribly since it's only fast for random access lists. You should always name things in a way agnostic to performance characteristics since those change over time.
3