[#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:68568] Re: [Ruby trunk - Feature #10982] Clarify location of NoMethod error
From:
İsmail Arılık <msms6174@...>
Date:
2015-03-20 07:27:31 UTC
List:
ruby-core #68568
``` foo.call && bar.call NoMethodError: undefined method `call' for nil:NilClass ``` I think this error already states that the method named `call` is undefined *for* the `nil` object of the `NilClass` class. So it is not necessary to change 'for' to 'on receiver'. 2015-03-20 0:47 GMT+02:00 <parkrmoore@gmail.com>: > Issue #10982 has been updated by Parker M. > > > This new syntax is a pretty sizable divergence from traditional Ruby error > reporting. At the moment, errors generally (always?) have an accompanying > stack trace: > > ```text > ~$ ruby errors.rb > errors.rb:2:in `<main>': undefined method `call' for nil:NilClass > (NoMethodError) > ``` > > It indicates the line, but excludes the column. It's uniform for all > errors, so users seeing these stack traces know in what file, what line, > and what method (the binding?) the error occurred. If the proposed format > were implemented, would it only be for NoMethodError's, or would it apply > to ArgumentError's or TypeError's, and so on? > > Would the column number suffice? So your example would yield: > > ```text > irb:1:16:in `<main>': undefined method `call' for nil:NilClass > (NoMethodError) > ``` > > You'd know that line 1 at column 16 caused the error. > > ---------------------------------------- > Feature #10982: Clarify location of NoMethod error > https://bugs.ruby-lang.org/issues/10982#change-51880 > > * Author: Richard Schneeman > * Status: Open > * Priority: Normal > * Assignee: > ---------------------------------------- > In Ruby, the error `NoMethodError` on happens frequently, especially when > it occurs on `nil`. This error can be confusing to beginners since, many of > them think there is a problem with the method instead of the receiver. This > error can be confusing to advanced developers when there are multiple > method calls in the on the same line. In this example it is unclear if > `foo` or `bar` returned `nil`: > > ``` > foo.call && bar.call > NoMethodError: undefined method `call' for nil:NilClass > ``` > > I would like to make this a better error message and to indicate where the > exception occurs. > > ``` > @foo.call && @bar.call > ^---- > NoMethodError: The method `call` is undefined on receiver nil:NilClass > ``` > > Now it is more clear that the `@bar` is currently `nil` and that is the > source of the error. I believe exposing this information will help > developers of all abilities. > > > > > -- > https://bugs.ruby-lang.org/ > -- 聴yi g端nler. 聴smail Ar脹l脹k