nice! been waiting on this one for ages. Any idea if removing the implicit box-ing that async_trait uses has a measurable impact on performance?
Are there some cases, say with really big futures, where removing the boxing actually hurts performance?
Are there some cases, say with really big futures, where removing the boxing actually hurts performance?
The future we're working toward is for this to be a decision you can make locally without introducing compatibility hazards or having to change a bunch of code. Ideally, one day you can even ask the compiler to alert you to potential performance hazards or make reasonable default choices for you...