[#68478] Looking for MRI projects for Ruby Google Summer of Code 2015 — Tony Arcieri <bascule@...>
Hi ruby-core,
10 messages
2015/03/10
[#68480] Re: Looking for MRI projects for Ruby Google Summer of Code 2015
— SASADA Koichi <ko1@...>
2015/03/10
I have.
[#68549] Re: Looking for MRI projects for Ruby Google Summer of Code 2015
— SASADA Koichi <ko1@...>
2015/03/17
I sent several ideas on previous, mail, but they are seems rejected?
[#68493] [Ruby trunk - Feature #10532] [PATCH] accept_nonblock supports "exception: false" — nobu@...
Issue #10532 has been updated by Nobuyoshi Nakada.
5 messages
2015/03/11
[#68503] Re: [Ruby trunk - Feature #10532] [PATCH] accept_nonblock supports "exception: false"
— Eric Wong <normalperson@...>
2015/03/12
Committed as r49948.
[#68504] Re: [Ruby trunk - Feature #10532] [PATCH] accept_nonblock supports "exception: false"
— Nobuyoshi Nakada <nobu@...>
2015/03/12
On 2015/03/12 12:08, Eric Wong wrote:
[#68506] Seven stacks (and two questions) — Jakub Trzebiatowski <jaktrze1@...>
The Ruby Hacking Guide says that Ruby has窶ヲ seven stacks. Is it an implementation choice (and it could be implemented with one stack), or is there really a need for seven logical stacks? For example, Lua has one stack, and still closures with upvalues are totally possible (it窶冱 like Ruby窶冱 blocks that can reference local variables of their enclosing method, but it works for any function with any upvalues).
5 messages
2015/03/12
[#68520] Possible regression in 2.1 and 2.2 in binding when combined with delegate? — Joe Swatosh <joe.swatosh@...>
# The following code
3 messages
2015/03/14
[#68604] GSOC project Cross-thread Fiber support — surya pratap singh raghuvanshi <oshosurya@...>
- *hi i am a third year computer science student interested in working
6 messages
2015/03/22
[#68606] Re: GSOC project Cross-thread Fiber support
— Tony Arcieri <bascule@...>
2015/03/22
Hi Surya,
[#68619] Re: GSOC project Cross-thread Fiber support
— surya pratap singh raghuvanshi <oshosurya@...>
2015/03/23
hi tony,
[ruby-core:68667] Re: [Ruby trunk - Bug #10967] [Open] Is "warning: private attribute?" wrong?
From:
Zachary Scott <e@...>
Date:
2015-03-28 08:36:28 UTC
List:
ruby-core #68667
I'd like to know the intention behind this warning.. but so far haven't seen it. Also, since this behavior was added in a minor release, we can't really change it now until the next major.. IF we care about semver for this, which may not be the case On Thursday, March 12, 2015, <santiago@wyeworks.com> wrote: > Issue #10967 has been updated by Santiago Pastorino. > > > One possible fix (the one removing the warning) ... > https://github.com/ruby/ruby/pull/849 > > ---------------------------------------- > Bug #10967: Is "warning: private attribute?" wrong? > https://bugs.ruby-lang.org/issues/10967#change-51839 > > * Author: Santiago Pastorino > * Status: Open > * Priority: Normal > * Assignee: > * ruby -v: ruby 2.3.0dev (2015-03-01 trunk 49796) [x86_64-darwin14] > * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN > ---------------------------------------- > The following code ... > > ``` > class Y > def initialize > @x = "ZOMG" > end > > def print_x > puts x > end > > private > > attr_reader :x > end > > Y.new.print_x > ``` > > outputs ... > > ``` > test.rb:12: warning: private attribute? > ``` > > I tend to think this warning is wrong, I was surprised by > https://github.com/rack/rack/pull/811 and I think this is a completely > valid use case. > > Also this code ... > > ``` > class Y > def initialize > @x = "ZOMG" > end > > def print_x > puts x > end > > def assign_x > self.x = "ZOMG ZOMG" > end > > private > > attr_accessor :x > end > > y = Y.new > y.assign_x > y.print_x > ``` > > Works fine with warnings also. So a private writer works ok when the > receiver is `self` because Ruby has a special case for it, this make me > think that private writers were thought to be used. > > So ... am I wrong thinking that the warning should be removed or the self > special case shouldn't work and be removed from Ruby code?. It doesn't make > sense to me to have both things. > > > > -- > https://bugs.ruby-lang.org/ >