Florian Zenker

I ran into this issue too but with box drawing characters. I believe that multibyte characters are not handled correctly. Not only do they not display correctly, the column position...

A test only bit like the one described is interesting, but it's slightly worrying that it would only be used by Bazel and Blaze (Blazel?) builds. OTOH, I am wondering...

> I'd also like to see some confirmation from someone that this is in fact useful for them and what they need I found this PR while trying to understand...

The order in which fields are serialized is left as an implementation detail. This allows for optimizations in the serialization path because the serializier doesn't need to worry about an...

Unfortunately, there is no support for this currently. Generally, the problem you describe is usually solved with areans, but we need to have Go language support for that: https://github.com/golang/go/issues/51317

You are right that it's probably not too hard to do, but it's going to be very hard to use correctly because one would need to ensure that the byte...

I don't understand how `slices.Clip` is relevant here. It doesn't change the aliasing problem.

That's unfortunately not the only issue. The slice can be modified by other means, in fact it's fairly common to reuse a byte slice. Consider this function: ```go func Parse(in...

We have a similar issue in with Google's internal peakheap profile implementation. As the name suggest, the peakheap profile keeps track of high-water-mark heap profiles. I was considering filing a...

Embedding a proto message like this ```go type embedMessage struct { *testpb.TestAllTypes } ``` Generates a lot of methods that forward to the generated `testpb.TestAllTypes` type. protocmp therefore thinks that...