If the user has a hfun which they call in the layout and so that is executed on every single page, the overhead due to the invokelatest (which can be of the order of 0.5s it seems) compounds.
Removing the invokelatest is not trivial. Maybe experimenting with Base.get_world_counter at some appropriate spot and Base.invoke_in_world would be acceptable. Note that the compounding effect is primarily noted at full pass where the user would not have a chance to modify Utils so it should be ok to freeze the method table...
If the user has a hfun which they call in the layout and so that is executed on every single page, the overhead due to the
invokelatest(which can be of the order of0.5sit seems) compounds.Removing the
invokelatestis not trivial. Maybe experimenting withBase.get_world_counterat some appropriate spot andBase.invoke_in_worldwould be acceptable. Note that the compounding effect is primarily noted at full pass where the user would not have a chance to modifyUtilsso it should be ok to freeze the method table...Dev: check
test/bugs/worldage