[#106355] [Ruby master Bug#18373] RBS build failure: '/include/x86_64-linux/ruby/config.h', needed by 'constants.o'. — "vo.x (Vit Ondruch)" <noreply@...>
Issue #18373 has been reported by vo.x (Vit Ondruch).
28 messages
2021/12/01
[ruby-core:106803] [Ruby master Bug#18241] Question on String Concatentation Documentation
From:
"nagachika (Tomoyuki Chikanaga)" <noreply@...>
Date:
2021-12-24 06:05:43 UTC
List:
ruby-core #106803
Issue #18241 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: REQUIRED to 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: DONE ruby_3_0 62a33dfa168504f8ee77d493979e66616ebe1da8 merged revision(s) c6706f15af123bdbb3b39a21903d85c78462d047. ---------------------------------------- Bug #18241: Question on String Concatentation Documentation https://bugs.ruby-lang.org/issues/18241#change-95612 * Author: hernanat (Anthony Hernandez) * Status: Closed * Priority: Normal * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: DONE ---------------------------------------- Hello, I noticed that the documentation for `<<` and `concat` both state that the result of each operation is a new string. However, while doing some experimenting myself I noticed that this doesn't seem to be the case. The result has the same object id and memory address as the initial string. I also noticed that the underlying C code fore both of these does seem to return the original string pointer at the end. Is this a documentation issue, or is there something else going on that I'm missing? If the former, I'm happy to put up a PR to fix. If it's the latter, I'd appreciate any explanation. Thanks Anthony -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>