[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
[email protected] wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
[email protected] wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85837] [CommonRuby Feature#14463] Allow comments to precede dots in member expressions
From:
shevegen@...
Date:
2018-02-27 02:14:04 UTC
List:
ruby-core #85837
Issue #14463 has been updated by shevegen (Robert A. Heiler).
> I still find it very odd that it's inconsistent.
Tsuyoshi Sawada pointed out something similar in the issue that
was referred to 5 years ago and I also agree with it.
I know little to nothing how ruby works internally but I would
have assumed that comments are completely ignored. Like "hello
ruby parser, ignore everything that comes on the line after a
'#' token". I should, however had, also say that I do not think
that I was ever affected by it; I don't think I wrote a .foo
method call on the next line, ever, in all my years of ruby. :)
The only excessive method chaining I sometimes do, but also quite
rarely, is something like this (semi-contrived):
object.sub(//,'').sub(//,'').sub(//,'').sub(//,'').
sub(//,'').sub(//,'').sub(//,'').sub(//,'')
And I already considered that pretty strange to do, but I do that
very rarely ... though never with the '.' dot on a newline.
----------------------------------------
Feature #14463: Allow comments to precede dots in member expressions
https://bugs.ruby-lang.org/issues/14463#change-70691
* Author: isiahmeadows (Isiah Meadows)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
I, coming from other languages, find it *extremely* odd that the first three are considered valid, but the fourth is a syntax error (tested in Ruby 2.3.4 + 2.5.0, Rubocop's parser for 2.3):
~~~ ruby
# 1
foo = -> {}
foo.
call
# 2
foo = -> {}
foo.
# comment
call
# 3
foo = -> {}
foo
.call
# 4
foo = -> {}
foo
# comment
.call
~~~
Any chance 4 could be fixed? (It looks more like a parser/spec bug than anything.)
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>