else? switch?

isn't it a bit overkill to have a qvector if we just have one function, and that one is even known at compile time?

I'd prefer if we simplify the code and make it only as complicated as needed:

std::transform(m_cachedLines.begin(), m_cachedLines.end(), KDevelop::stripAnsiSequences);

also, if we decide to keep it as complex as it is currently, I'd suggest you flip the order of the loops. the number cached lines is most of the time going to be much larger than the number of filter functions. thus looping over them first reduces cache misses.

Removed the vector, and turned std::for_each into std::transform.

Cheers,
Kevin

commit ee3d0a311c10b6c46b04cd950d6b0f4272fd6e49
Author: Kevin Funk <kfunk@kde.org>
Date:   Thu Dec 17 14:57:17 2015 +0100

    OutputModel: Reduce complexity re. pre-filtering
    
    Less extendable now, but it's also questionable if we ever need to extend
    it.
    
    Addresses Milian's concerns.