New: CPArray -arrayByApplyingBlock:

[cacaodev]

This new method maps the receiver using the provided function.
Similar to javascript or swift map function.

There are tens of places in the fmw where using this method can reduce the amount of code.

With test.

[cappbot]

Milestone: Someday. Label: #new. What's next? A reviewer should examine this issue.

[cappbot]

Milestone: Someday. Labels: #needs-review, Foundation, feature. What's next? This issue is pending an architectural or implementation design decision and should be discussed or voted on.

[cacaodev]

It appears that Array.map is a lot slower than for loops. An example here : https://jsperf.com/map-vs-native-for-loop/7

As a consequence, I will remove the native map but I still believe cappuccino needs a map API because it is very common in most languages.
The naming could also be better.
What about -arrayByApplyingBlock: ? More consistent with other CPArray methods naming and express better the fact that it is an immutable method. And the array prefix tells clearly what it returns.
Of course, in js Block should be Function but we already use Block for other array methods that take a function arg.
@cappuccino/core-devs what do you think ?

[aparajita]

I agree with -arrayByApplyingBlock: as the name.

[aljungberg]

I agree, arrayByApplyingBlock is more consistent. Methods that return something tend to be named by what they return, like arrayByAddingObject.

(Often we say UsingBlock -- arrayByUsingBlock doesn't sound as clear though. I like your naming, arrayByApplyingBlock, better.)

+#needs-improvement

[cappbot]

Milestone: 0.9.9. Labels: #needs-improvement, #needs-review, Foundation, feature. What's next?

• This issue is pending an architectural or implementation design decision and should be discussed or voted on.
• The code for this issue has problems with formatting or fails a capp_lint check, has bugs, or has non-optimal logic or algorithms. It should be improved upon.

[aparajita]

Merci!

[cacaodev]

Merged, thanks for your input.