Issue #19315 has been updated by kou (Kouhei Sutou). Eregon (Benoit Daloze) wrote in #note-30:
1. Deprecate `RSTRING_PTR()` with a message saying to use either `StringValueCStr()` (if want to use it as a NUL-terminated C string) or `RSTRING_START()` (for efficiency & fixing the warning, must be paired with either `RSTRING_LEN()` or `RSTRING_END()`). ... 3. Then some release(s) later enable `SHARABLE_MIDDLE_SUBSTRING`. `RSTRING_PTR()` at that point is the same as `RSTRING_START()` (so no issues with using a different buffer than `RSTRING_END()` and already-correct usages of `RSTRING_PTR` are preserved even if they didn't migrate), but no longer guarantees to be NUL-terminated (which was already incorrect for the `\0` in the middle case and should have used `StringValueCStr()` already).
I object deprecating `RSTRING_PTR()` and changing its behavior later. Because it breaks backward compatibility. We should not break backward compatibility as much as possible to not increase maintenance costs of existing gem maintainers. I think that adding a new API and keep compatibility of existing APIs is better. ---------------------------------------- Feature #19315: Lazy substrings in CRuby https://bugs.ruby-lang.org/issues/19315#change-117488 * Author: Eregon (Benoit Daloze) * Status: Open ---------------------------------------- CRuby should implement lazy substrings, i.e., "abcdef"[1..3] must not copy bytes. Currently CRuby only reuse the char* if the substring is until the end of the buffer. But it should also work wherever the substring starts and ends. Yes, it means RSTRING_PTR() might need to allocate to \0-terminate, so be it, it's worth it. There is already code for this (`SHARABLE_MIDDLE_SUBSTRING`), but it's disabled by default and `RSTRING_PTR()` needs to be changed to deal with this. It seems a good idea to introduce a variant of `RSTRING_PTR` which doesn't guarantee \0-termination, so such callers can then use the existing bytes always without copy. There are countless workarounds for this missing optimization, all not worth it with lazy substring and all less readable: * https://bugs.ruby-lang.org/issues/19314 * https://bugs.ruby-lang.org/issues/18598#note-3 * https://github.com/ruby/net-protocol/pull/14 * Manual lazy substrings which track string + index + length * More but I don't remember all now, feel free to comment or link more urls/tickets. -- https://bugs.ruby-lang.org/