I think going this way is going to turn out painful. The sort of immutable container logic that people associate with FP is against the nature of C++ and you'll be constantly bumping into other people's code, and parts of the library, that don't like it. C++ style prefers for_each(xs.begin(), xs.end(), f); to xs = std::transform(xs,f); Because the first does not copy the container and its elements, which in C++ is a…
> The sort of immutable container logic that people associate with FP is against the nature of C++... My argument is that C++, a multi-paradigm language, benefits from not being bound to purity and that being able to mix imperative and functional code is a good thing. We aren't stuck in pure-land so we can insert IO where it needs to be, not where it propagates, but neither do we need to be stuck in state-land. Funct…
Re: Manipulating C++ Containers Functionally
#11Yeah, but those "implementation details" are often relevant. I want to know if I am creating a bunch of extraneous copies when iterating through a container. It may not always matter, but sometimes it does, and performance matters more than functional purity.