From: me@... Date: 2018-02-27T01:06:54+00:00 Subject: [ruby-core:85834] [CommonRuby Feature#14463] Allow comments to precede dots in member expressions Issue #14463 has been updated by isiahmeadows (Isiah Meadows). duerst (Martin D��rst) wrote: > There is extensive discussion on this at #7636. Please check. I presume you meant #7639... I never found that due to probably its age and the fact it was in the other project. I still find it very odd that it's inconsistent. The alternative to my proposal would be to make the third also error (as I presume it did previously), so it'll remain consistent across both. (Ruby isn't my primary language, so I'm still getting used to the language-level preference for dot-last.) ---------------------------------------- Feature #14463: Allow comments to precede dots in member expressions https://bugs.ruby-lang.org/issues/14463#change-70688 * 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: