Rails中Role.all.map(&:id)里&:id的作用及字段方法调用问题

Hey there! Let's unpack your questions about Ruby/Rails syntax step by step.

You're absolutely right that &:id is a shorthand for {|role| role.id}. Here's the breakdown:

• The & operator in Ruby takes an object and tries to convert it into a Proc (a reusable block) by calling its to_proc method.
• Ruby's Symbol class has a built-in to_proc method. When you write &:id, Ruby does something like this under the hood:

  Role.all.map(&:id.to_proc)
  

• The :id.to_proc returns a Proc that behaves like proc { |obj| obj.id }. So when map runs, it passes each Role instance to this Proc, which calls the id method on it.

When you tried Role.all.map(&:id.to_s), you got an error because :id.to_s returns the string "id"—and strings don't have a to_proc method Ruby can use with the & operator. Here are the most practical solutions to run a method on a specific field:

Option 1: Use a regular block (simplest and most readable) #

This is the straightforward approach that’s easy for anyone reading your code to follow:

Role.all.map { |role| role.id.to_s }

Option 2: Use pluck + map (more efficient for Rails) #

If you only need the id values (not full Role objects), pluck is better—it fetches just the id column directly from the database (instead of loading entire records). Then you can convert those ids to strings in memory:

Role.pluck(:id).map(&:to_s)

This is way faster than loading all Role instances, especially with large datasets.

Option 3: Build a custom Proc (for learning how & works) #

If you want to stick with the & syntax, you can create a custom Proc explicitly:

# Using proc
Role.all.map(&proc { |role| role.id.to_s })

# Or using lambda (slight behavior differences, but works here)
Role.all.map(&lambda { |role| role.id.to_s })

This is more verbose than the block approach, but it makes it clear that & expects a Proc.

Option 4: Functional composition (Ruby 2.6+) #

For a more advanced, functional programming-style approach, you can chain Procs using >> (available in Ruby 2.6+):

id_proc = proc { |role| role.id }
to_s_proc = method(:to_s).to_proc
Role.all.map(&id_proc >> to_s_proc)

This first runs the id_proc to get the role's id, then passes that result to to_s_proc to convert it to a string. It's a neat trick, but overkill for most everyday cases.

内容的提问来源于stack exchange，提问作者MEENAKSHI KUMARI