Aleksey Shipilëv

Good stuff. Actually, let me see how easy it is to implement the `nofast_*` bytecodes in Zero, so we don't have to do the shared-code exceptions for it.

> Good stuff. Actually, let me see how easy it is to implement the `nofast_*` bytecodes in Zero, so we don't have to do the shared-code exceptions for it. That...

> > Good stuff. Actually, let me see how easy it is to implement the `nofast_*` bytecodes in Zero, so we don't have to do the shared-code exceptions for it....

> > Do you know how much testing is done by the community with zero? We don't test it that much in our pipeline. > > You could ask the...

> Maybe so, but I think direct allocation of 1.5x size may reduce the number of allocations in some extreme cases. On the other hand, it might also waste memory...

Any thoughts?

Thank you! Any other comments? I'll be integrating it soon otherwise.

> I'm confused. How does adding EnsureCapacity in newString646_US fix the compiler warning mentioned in JBS? I think this is a bona-fide compiler static analyzer bug. GCC 12 compiles this...

Thanks! /integrate

Paging @iklam ;)