[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bytevector-string-ref
From: |
Vijay Marupudi |
Subject: |
Re: bytevector-string-ref |
Date: |
Sun, 18 Dec 2022 10:35:40 -0600 |
The 2 copies occur if you want a portion of the bytevector to be
converted to a string. The current API requires you to copy to a
bytevector that's the length of the slice, and then convert that copy to
a string.
I've sent patches to guile-devel to address this issue (by extending
utf{8,16,32}->string) in the past, but those patches have not gotten any
attention yet.
Attaching them again here to (hopefully) revive them.
0001-Allow-utf8-string-utf16-string-utf32-string-to-take-.patch
Description: Text Data
~ Vijay
- bytevector-string-ref, Sascha Ziemann, 2022/12/18
- Re: bytevector-string-ref, tomas, 2022/12/18
- Re: bytevector-string-ref, Taylan Kammer, 2022/12/18
- Re: bytevector-string-ref, Matt Wette, 2022/12/18
- Re: bytevector-string-ref, Sascha Ziemann, 2022/12/18
- Re: bytevector-string-ref, tomas, 2022/12/19
- Re: bytevector-string-ref, Sascha Ziemann, 2022/12/21
- Re: bytevector-string-ref, tomas, 2022/12/22
- Re: bytevector-string-ref, Sascha Ziemann, 2022/12/22
- Re: bytevector-string-ref, lloda, 2022/12/22