2 ms·

Thank you for your reply. I was thinking about whether to return an error. If we can’t find a UTF-8 start byte in the nearby 4 bytes, it’s unclear what to retu

Thank you for your reply. I was thinking about whether to return an error. If we can’t find a UTF-8 start byte in the nearby 4 bytes, it’s unclear what to return. I thought maybe we could ignore this problem. I don’t return the string itself because I don’t know if users want the start or the end of the string. Also, I want to avoid copying large strings. It’s up to the users how they use this function. Since no one is using this package yet, we might consider changing the interface.

lifthrasiir 2y ago
> I was thinking about whether to return an error. If we can’t find a UTF-8 start byte in the nearby 4 bytes, it’s unclear what to return. I thought maybe we could ignore this problem. This highly depends on the use case, and your stated use case doesn't seem to need any sort of error. > Also, I want to avoid copying large strings. Go strings are not copied in that way; they are implemented like immutable slices [1]. [1] https://research.swtch.com/godata https://research.swtch.com/godata