[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>
I would like to request developers meeting around April 17 or 18 in this month.
14 messages
2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014
— Urabe Shyouhei <shyouhei@...>
2014/04/03
It's good if we have a meeting then.
[#61826] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/03
Regarding openssl issues, I’ve discussed possible meeting time with Martin last month and he seemed positive.
[#61833] Re: Plan Developers Meeting Japan April 2014
— Martin Bo煬et <martin.bosslet@...>
2014/04/03
Hi,
[#61847] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/03
Martin Boテ殕et <martin.bosslet@gmail.com> wrote:
[#61849] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I will post summary of meeting on Google docs after the meeting.
[#61852] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/04
Zachary Scott <e@zzak.io> wrote:
[#61860] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I’m ok with redmine, thanks for bringing up your concern!
[#62076] Candidacy to 2.1 branch maintainer. — Tomoyuki Chikanaga <nagachika00@...>
Hello,
7 messages
2014/04/17
[#62078] Re: Candidacy to 2.1 branch maintainer.
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/04/17
> And does anyone have counter proposal for 2.1 maintenance?
[ruby-core:62164] [ruby-trunk - Feature #8956] [Rejected] Allow hash members delimited by \n inside of {}
From:
nobu@...
Date:
2014-04-26 01:24:43 UTC
List:
ruby-core #62164
Issue #8956 has been updated by Nobuyoshi Nakada.
Description updated
Status changed from Open to Rejected
It seems this issue has diverged so far from the original.
I reject it for now.
----------------------------------------
Feature #8956: Allow hash members delimited by \n inside of {}
https://bugs.ruby-lang.org/issues/8956#change-46321
* Author: Adam Dunson
* Status: Rejected
* Priority: Normal
* Assignee:
* Category: core
* Target version:
----------------------------------------
Currently, hashes require members to be delimited by commas (`,`), even inside curly braces. E.g.,
~~~ruby
some_hash = {
:foo => 'bar',
:bar => 'foo',
:baz => {
:qux => 'quux',
:corge => 'grault'
}
}
~~~
In my opinion, these commas add nothing of value to this particular example since, visually, the members are already delimited by a newline (`\n`). Additionally, missing a comma between members results in `syntax error, unexpected tSYMBEG, expecting '}'`.
I propose we make these commas optional, such that the following syntax would be possible:
~~~ruby
some_hash = {
:foo => 'bar'
:bar => 'foo'
:baz => {
:qux => 'quux'
:corge => 'grault'
}
}
~~~
This change would not affect existing hashes. Developers would be able to mix and match the old and new syntaxes as such:
~~~ruby
some_hash = {
:foo => 'bar'
:bar => 'foo'
:baz => {
:foo => 'bar' + 'baz'
:bar => 'foo', :qux => 'quux'
:corge => 'grault'
}
}
~~~
This change would also reduce the occurrence of syntax errors in cases where the developer temporarily replaces a value in the hash, e.g.,
~~~ruby
some_hash = {
:this => 'that',
:foo => 'not bar'#'bar',
:those => 'the other'
}
~~~
Finally, this change would only affect hashes inside curly braces (for hopefully obvious reasons).
I have attached a diff of my suggested changes along with a script to test a variety of use cases. I also have an open pull request on GitHub: URL:https://github.com/ruby/ruby/pull/402
Please let me know if there's anything I've missed or that needs clarification.
---Files--------------------------------
fix-hash-delims.patch (1.37 KB)
hash-test.rb (1.05 KB)
add-array-support.patch (2.6 KB)
add-method-arg-support.patch (2.48 KB)
add-method-arg-support-FIXED.patch (2.32 KB)
no-comma-tests.patch (2.38 KB)
comic-pet-desktop-very-happy-cat.jpg (457 KB)
--
https://bugs.ruby-lang.org/