Hi @makenowjust,

Not sure about this change. I know space can make a difference (the +1 case), but I don't see a reason to allow a space before a block argument. The lack of a space between & and the next word makes it super obvious that it's a block argument and it's visually more easy to spot.

Why do you need this?

I write long method chain with new line, see following:

foo(&
  .it_s(:long)
  .method
  .chain(:foo, :bar))

and, above example can rewrite by using itself for current compiler:

foo(&.itself
  .it_s(:long)
  .method
  .chain(:foo, :bar))

I think such a meaningless method call makes us confused on code reading, so it should be removed.

(Note: this fix cannot change to parse above code because parse_call_block_args dosen't skip newline, however I think this fix is one step to it.)

@makenowjust You can write it like this:

foo(&.it_s(:long)
     .method
     .chain(:foo, :bar))

I'd like to keep the meaning of & right next to the following expression as meaning "block argument". This is similar to splat *arg and double splat **arg, and it makes code more visually clear.

I don't think this use case justifies this change, as there's a way to write it, and it's maybe not that frequent, so I'll close this.