[#75687] [Ruby trunk Bug#12416] struct rb_id_table lacks mark function — shyouhei@...
Issue #12416 has been reported by Shyouhei Urabe.
3 messages
2016/05/23
[#75763] [Ruby trunk Feature#12435] Using connect_nonblock to open TCP connections in Net::HTTP#connect — mohamed.m.m.hafez@...
Issue #12435 has been reported by Mohamed Hafez.
3 messages
2016/05/28
[#75774] Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock — Mohamed Hafez <mohamed.m.m.hafez@...>
Hi all, every now and then in my production server, I'm
4 messages
2016/05/30
[#75775] Re: Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock
— Mohamed Hafez <mohamed.m.m.hafez@...>
2016/05/30
Or does MRI's OpenSSL::SSL::SSLSocket#connect_nonblock just return
[#75782] Important: Somewhat backwards-incompatible change (Fwd: [ruby-cvs:62388] duerst:r55225 (trunk): * string.c: Activate full Unicode case mapping for UTF-8) — Martin J. Dürst <duerst@...>
With the change below, I have activated full Unicode case mapping for
4 messages
2016/05/31
[ruby-core:75667] [Ruby trunk Feature#12263] Feature request: &&. operator (shorthand for foo && foo.method)
From:
danieldasilvaferreira@...
Date:
2016-05-22 05:59:35 UTC
List:
ruby-core #75667
Issue #12263 has been updated by Daniel Ferreira. By implementing https://bugs.ruby-lang.org/issues/12412 We would get the desired behaviour: ~~~ ruby false&.class # => FalseClass false&.inexisting # => nil ~~~ For me the situation: ~~~ ruby false&.class ~~~ it is a particular situation that can be handle using extra logic. I don't think there are enough case situations to add a new operator to the language. And by extending the safe navigation operator we will be making use of an already existent language feature. ---------------------------------------- Feature #12263: Feature request: &&. operator (shorthand for foo && foo.method) https://bugs.ruby-lang.org/issues/12263#change-58797 * Author: Johnny Shields * Status: Feedback * Priority: Normal * Assignee: ---------------------------------------- Ruby 2.3 introduced the `&.` safe-navigation operator. I'd like to propose a `&&.` operator which would be shorthand for: ~~~ruby foo && foo.method ~~~ Unlike `&.`, this does not continue the chain if the variable evaluates to `false`. This would give the following result: ~~~ruby false&.class # => FalseClass false&&.class # => false false&.inexisting # => raises NoMethodError false&&.inexisting # => false ~~~ -- 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>