Conversation
|
Looks very good and smart to me! But I think we need to test the performance penalty before merging it. Thanks! |
|
Not so great:
|
|
If this performance downgrade is not due the compilation flags, I think we should try to improve the performance of this approach before merging it because the performance regression is significant. |
|
I have run the benchmarks with the Cargo.toml optimizations and the difference of performance hurts 😞 :
|
|
I guess it's pretty conclusive anyway but |
|
It has many outliers and maybe there are instruction cache misses? I don't know, I executed the benchmarks without executing other CPU-intensive tasks, but an additional benchmark would be desirable to verify the performance loss. |
|
I did some profiling on Abandoning this PR for now. I will preserve the branch in my own fork. |

Stacked on top of #880
As discussed in #870 (comment), instead of
write
At the same time we can make
StrWriteand friends private and less complicated.I haven't evaluated the performance implications of this yet.