[#68845] [Ruby trunk - Feature #11056] [PATCH] lib/net/*: use io/wait methods instead of IO.select — normalperson@...
Issue #11056 has been updated by Eric Wong.
3 messages
2015/04/11
[#68945] [Ruby trunk - Feature #11083] [Open] Gemify net-telnet — shibata.hiroshi@...
Issue #11083 has been reported by Hiroshi SHIBATA.
4 messages
2015/04/21
[#68951] Re: [Ruby trunk - Feature #11083] [Open] Gemify net-telnet
— Eric Wong <normalperson@...>
2015/04/21
shibata.hiroshi@gmail.com wrote:
[#69012] [Ruby trunk - Feature #11105] [Open] ES6-like hash literals — shugo@...
Issue #11105 has been reported by Shugo Maeda.
5 messages
2015/04/29
[ruby-core:68751] [Ruby trunk - Feature #11032] Add a warning for misspelling "def intialize"
From:
matthew@...
Date:
2015-04-04 01:55:57 UTC
List:
ruby-core #68751
Issue #11032 has been updated by Matthew Kerwin. Jeremy Evans wrote: > What if I misspelled it "initailize"? Or "initalize"? Or any other of the numerous different ways to misspell it? Or "initialise"? Which I do with some regularity. My solution: unit testing. ---------------------------------------- Feature #11032: Add a warning for misspelling "def intialize" https://bugs.ruby-lang.org/issues/11032#change-52030 * Author: Robert A. Heiler * Status: Open * Priority: Low * Assignee: ---------------------------------------- Hi guys, When I was younger, in a class, I wrote this: "def intialize(some_argument_here)" This lead to an error because it should have been: "def initialize(some_argument_here)" My proposal is simple: Add a warning for an error like this. :) (a) If there is no method called "initialize" (b) but there is a message called "intialize", in a given class, add a notification such as: "warning: intialize might be misspelled, perhaps you meant initialize" Reasoning: Perhaps other people out there also sometimes misspell initialize, so that might make it a bit faster for them to detect this error. -- https://bugs.ruby-lang.org/