From: daniel@...42.com Date: 2019-10-24T14:09:11+00:00 Subject: [ruby-core:95532] [Ruby master Feature#16275] Revert `.:` syntax Issue #16275 has been updated by Dan0042 (Daniel DeLorme). mame (Yusuke Endoh) wrote: > I'm currently thinking that the following design is preferable. > > * A plain old style should be the base: `.map {|x| x.to_s(16) }` `.map {|x| JSON.parse(x) }` > * A numbered parameter makes simple cases simpler: `.map { _1.to_s(16) }` `.map { JSON.parse(_1) }` > * #16120 is worth reconsidering which makes typical case rather simpler: `.map { .to_s(16) }` (and this style is more flexible than the current `.map(&:to_s)`) > * `.map(&:to_s)` should be deprecated I agree with all the above. And if you can get Matz to reconsider #16120 nothing could make me happier :-) But since I prefer `map(&:to_s)` to `map{_1.to_s}`, deprecating the former without #16120 would be rather painful. ---------------------------------------- Feature #16275: Revert `.:` syntax https://bugs.ruby-lang.org/issues/16275#change-82308 * Author: naruse (Yui NARUSE) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- `obj.:method` is introduced at r66667 by #12125 and #13581. It encourages the functional programming style in Ruby. But this shorthand syntax is just for methods of `self` without arguments. It causes another feature requests like #16273 (and lambda compositions like #15428). Such features will introduce a new view of Ruby but no one illustrates the whole picture yet. I worried about such patch work may cause a conflict with future expansion of functional programing style or a just a garbage feature. `.:` syntax is introduced in 2.7.0 preview1, not released in production yet. How about reverting at this time and re-introduce with a big picture. -- https://bugs.ruby-lang.org/ Unsubscribe: