News for hackers. Stuff that matters.
Re:"Useless syntax sugar": Numbered block parameters in Ruby by dragonwriter on Wednesday October 11, 2023 @01:51PM (#37847839)
> It is only happenstance that ruby allows this form for methods only via `users.map(&:some_method)`, and we are stuck with forced variable names when calling other functions.

Not sure what you are trying to say here, because there are so much odd about this that it is hard to penetrate.

First, & works on proc-able objects (those that are Procs or can be converted to them via #to_proc), not "methods", and what you show it being used with is a symbol, not a method. Symbol#to_proc on a symbol s produces a proc that is functionally something like:

  ->(*args, **kwargs) { args[0].send(s, args[1..-1, **kwargs] }
While that's complicated, the upshot is that it creates a proc that calls the method whose name is the symbol & was applied to on its first argument, passing its remaining arguments as the arguments to the method.

> What we really want is `users.map{ do_something }`.

But if you want to pass a method on self, the only thing in Ruby that you can call like do_something(x), to map, you can do that without an expllcit block already, by using the Object#method method, which returns a Proc that is equivalent to calling the method:

  users.map &method(:do_something)
And if you want to call a Proc object in a local variable called do_something to map (the closest thing to a "non-method function" that exists in Ruby), you can do that without an explicit block, even more concisely, because you don't have to convert it to a Proc first:

  users.map &do_something
Re:"Useless syntax sugar": Numbered block parameters in Ruby by jonahx on Wednesday October 11, 2023 @02:40PM (#37848534)
Sigh. Yes, I am aware of the technicalities you describe. I thought my point was clear without my needing to be pedantically accurate.

In many languages (even in JS!) you can just map a function point-free, rather than having to introduce a variable just because syntax demands it, or worry about which syntax to use depending on if the "function" you're calling is a method on the object being mapped or something else. It's all noise.

> you can do that without an expllcit block already, by using the Object#method method, which returns a Proc that is equivalent to calling the method:

> users.map &method(:do_something)

Again, I am aware, and the ugliness of that solution proves the point I was trying to make -- it is even worse than the block syntax with a variable.

Re:"Useless syntax sugar": Numbered block parameters in Ruby by dragonwriter on Wednesday October 11, 2023 @02:54PM (#37848720)
> In many languages (even in JS!) you can just map a function point-free,

Yes, in many languages, "functions" are a thing that exists. In Ruby, there is no such thing as a function. The concept does not exist.

Which is why it is bizarre to talk about what you can and can't do with "functions" in Ruby, and to call kinds of different not-function things (including symbols, of all things) "functions" in that discussion. Its just applying language that makes no sense.