[#79440] [Ruby trunk Bug#13188] Reinitialize Ruby VM. — shyouhei@...
SXNzdWUgIzEzMTg4IGhhcyBiZWVuIHVwZGF0ZWQgYnkgU2h5b3VoZWkgVXJhYmUuCgoKTWFydGlu
6 messages
2017/02/06
[#79441] Re: [Ruby trunk Bug#13188] Reinitialize Ruby VM.
— SASADA Koichi <ko1@...>
2017/02/06
On 2017/02/06 10:10, shyouhei@ruby-lang.org wrote:
[#79532] Immutable Strings vs Symbols — Daniel Ferreira <subtileos@...>
Hi,
15 messages
2017/02/15
[#79541] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/15
Em 15-02-2017 05:05, Daniel Ferreira escreveu:
[#79543] Re: Immutable Strings vs Symbols
— Daniel Ferreira <subtileos@...>
2017/02/16
Hi Rodrigo,
[#79560] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/16
Em 15-02-2017 22:39, Daniel Ferreira escreveu:
[ruby-core:79611] Re: Immutable Strings vs Symbols
From:
Daniel Ferreira <subtileos@...>
Date:
2017-02-19 23:08:11 UTC
List:
ruby-core #79611
Hi Rodrigo,
>
> From your comments I'm guessing you haven't actually read those discussions.
> If this is true, I'd certainly advise you to read the discussion before
> creating a new ticket, as the discussion itself is not outdated from my
> point of view.
>
From the two requests I've read the following Matz comments:
"Hi,
During early stage of 1.9 development, I tried to make symbols and
strings behave same (at least similar), and it had broken too many
programs. I understand your problem but it's not worth raising huge
compatibility issues.
matz.
"
"
Hi,
Two points:
(1) Currently symbols and strings are very different in several
aspect. Making them "compatible" would break backward
compatibility.
(2) "==" and "===" have different roles from PHP. So your logic is
incomplete. I suggest to learn "Ruby Way", before proposing
language changes to Ruby.
So in summary, this proposal is half-baked. Need to be more concrete.
matz.
"
There are challenges but maybe we can find a solution that would be
feasible in Ruby 3.
I would like to start a new discussion about this subject because I
deeply believe ruby will be better if we succeed to do so.
As I see it, everyone agrees there is a problem.
We just weren't able to find the best solution to resolve it.
Lets try to do that in Ruby 3.
Thanks,
Daniel
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>