[#69892] [Ruby trunk - Feature #11339] [Open] [PATCH] io.c: avoid kwarg parsing in C API — normalperson@...
Issue #11339 has been reported by Eric Wong.
8 messages
2015/07/07
[#69983] Re: [Ruby trunk - Feature #11339] [Open] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/07/15
normalperson@yhbt.net wrote:
[#69990] Re: [Ruby trunk - Feature #11339] [Open] [PATCH] io.c: avoid kwarg parsing in C API
— SASADA Koichi <ko1@...>
2015/07/16
On 2015/07/16 4:41, Eric Wong wrote:
[#69995] Re: [Ruby trunk - Feature #11339] [Open] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/07/16
SASADA Koichi <ko1@atdot.net> wrote:
[#69984] $SAFE inside an Array — Bertram Scharpf <lists@...>
Hi,
4 messages
2015/07/15
[#70001] [Ruby trunk - Bug #11336] [Open] TestProcess#test_exec_fd_3_redirect failed on Solaris 10 — ngotogenome@...
Issue #11336 has been updated by Naohisa Goto.
4 messages
2015/07/16
[#70005] Re: [Ruby trunk - Bug #11336] [Open] TestProcess#test_exec_fd_3_redirect failed on Solaris 10
— Eric Wong <normalperson@...>
2015/07/16
Sorry, but I think rb_divert_reserved_fd seems a racy fix. I think the
[#70011] [Ruby trunk - Bug #11362] [Open] [PATCH] ensure Process.kill(:STOP, $$) is resumable — normalperson@...
Issue #11362 has been reported by Eric Wong.
3 messages
2015/07/17
[#70016] [Ruby trunk - Bug #11364] [Open] Use smaller buffer for sendmsg — merch-redmine@...
Issue #11364 has been reported by Jeremy Evans.
8 messages
2015/07/17
[#70052] Re: [Ruby trunk - Bug #11364] [Open] Use smaller buffer for sendmsg
— Eric Wong <normalperson@...>
2015/07/20
merch-redmine@jeremyevans.net wrote:
[#70055] Re: [Ruby trunk - Bug #11364] [Open] Use smaller buffer for sendmsg
— Jeremy Evans <code@...>
2015/07/20
On 07/20 10:46, Eric Wong wrote:
[#70056] Re: [Ruby trunk - Bug #11364] [Open] Use smaller buffer for sendmsg
— Eric Wong <normalperson@...>
2015/07/21
Jeremy Evans <code@jeremyevans.net> wrote:
[#70103] [Ruby trunk - Feature #11375] Decreased Object Allocation in Pathname.rb — richard.schneeman@...
Issue #11375 has been updated by Richard Schneeman.
3 messages
2015/07/23
[#70156] [Ruby trunk - Bug #11396] Bad performance in ruby >= 2.2 for Hash with many symbol keys — dunric29a@...
Issue #11396 has been updated by David Unric.
3 messages
2015/07/28
[ruby-core:70027] [Ruby trunk - Misc #11372] [Rejected] Confusing a+b=9 ... unintented behavior, valid statement
From:
matz@...
Date:
2015-07-18 11:17:56 UTC
List:
ruby-core #70027
Issue #11372 has been updated by Yukihiro Matsumoto. Status changed from Open to Rejected Hi, Although I can understand how you feel, the change will break millions of Ruby programs. There could be milder option, like warning for certain usege of equal sign in expressions. Matz. ---------------------------------------- Misc #11372: Confusing a+b=9 ... unintented behavior, valid statement https://bugs.ruby-lang.org/issues/11372#change-53452 * Author: Dug Dough * Status: Rejected * Priority: Normal * Assignee: ---------------------------------------- Hello, I found that when = is written instead of ==, it can cause unintended effects and it is hard to notice this typo, because it is valid statement. For example valid statement a+b=7 ,due to the everything is a expression, is treated as a+(b=11) and not interpreted as syntax error, like in other languages. Should't be this behavior changed? My suggestion is to make the assignment operator unable to be used as expresion (syntactically). It would prevent that mistakes. Optionally (for 'backward compatibility', or 'override'), assignment enclosed in parentheses would still be treated as expression , that would make a+(b=9) valid. The meaning of extra parentheses would mean "This is not mistake, i want to use the value of variable b as expression". -- https://bugs.ruby-lang.org/