(#6016) - separate funcs for map vs reduce #6016

Merged
merged 1 commit into from Dec 21, 2016

Projects

None yet

2 participants

@nolanlawson
Member

This is another function that showed up as a major offender in terms of unnecessary memory allocations. But given that we only need to allocate new memory during the custom reduce functions (which are rarer than the custom map functions), this is a fairly easy fix.

@nolanlawson nolanlawson changed the title from (#6015) - separate funcs for map vs reduce to (#6016) - separate funcs for map vs reduce Dec 16, 2016
@nolanlawson nolanlawson (#6016) - separate funcs for map vs reduce
b260d08
@daleharvey daleharvey merged commit 85694c2 into master Dec 21, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 100.0%
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment