On 8/13/25 2:48 PM, John Ericson wrote:
A follow-up from "driver: Rework for_each_path using C++"
These types are, for all intents and purposes, single-use closure
environment types. It is much more ergonomic to just use lambdas for
this.
On IRC there was concern about static dispatch and compile times with
lambdas,
As I mentioned in a previous reply, I think those concerns were
overblown; it would be worth comparing the 'size' of xgcc before and
after such a change, but I wouldn't expect it to be significant.
but I have kept the class hierarchy and virtual methods from
the previous commit that keeps `find_within_paths::for_each_path`
untemplated, and I believe that addresses the issue.
But it leaves us with a weird mash-up of static and dynamic polymorphism
that doesn't strike me as clearer. I'd rather have just one or the other.
Jason
