4 ms·
a better idea is to first use filter() to obtain a collection you can then map() over. So then you dont need to continue or break, the offending elements of the
by bil7 5y ago
a better idea is to first use filter() to obtain a collection you can then map() over. So then you dont need to continue or break, the offending elements of the collection were already filtered out.
- thfuran 5y agoBut then you're processing the whole list, probably defeating the point of breaking.
- bil7 5y agoi don't understand what you mean. Are you referring to performance or implementation details?
- appletrotter 5y agothat's a performance optimization. you have other performance optimizations available often, with tradeoffs. FP is a higher level paradigm so you might have to trade off with performance too
- thfuran 5y ago>FP is a higher level paradigm so you might have to trade off with performance too Then it can hardly he said be to unequivocally be better, can it.
- 0ldskool 5y agothat's like saying high level languages cannot be unequivocally better then writing assembly, not doing your own memory management is bad, etc... Functional programming is a higher level abstraction. If the underlying implementation is not well implemented/optimized then you could have bad performance while the opposite is also true.
- thfuran 5y ago>that's like saying high level languages cannot be unequivocally better then writing assembly, Yes, it is like saying that. At least, assuming by "cannot be" you mean "is not". >not doing your own memory management is bad No, it's not like saying that. Note how differently those claims are phrased.