Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 304395
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T07:16:36+00:00 2026-05-12T07:16:36+00:00

(Sorry for the newbie question.) In Ruby, what is the difference between the loops:

  • 0

(Sorry for the newbie question.) In Ruby, what is the difference between the loops:

@cars.each do |car| 

and

for car in @cars do

?

is there a difference in efficiency, or why do we need two (or more) ways to express the same thing? The second way seems more elegant/natural to me, but I may be missing some crucial observation, why the first may be the better choice.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T07:16:37+00:00Added an answer on May 12, 2026 at 7:16 am

    More people use the @cars.each notation because that generalizes to other methods (like #inject, #each_with_index, #map, etc, as well as non-iterator callbacks).

    for/in is mainly just syntactic sugar for #each. The main difference in how the two work is in variable scoping:

    irb> @cars = %w{ ford chevy honda toyota }
    #=> ["ford", "chevy", "honda", "toyota"]
    irb> @cars.each { |car| puts car }
    ford
    chevy
    honda
    toyota
    #=> ["ford", "chevy", "honda", "toyota"]
    irb> car
    NameError: undefined local variable or method `car` for #<Object:0x399770 @cars=["ford", "chevy", "honda", "toyota"]>
            from (irb):3
            from /usr/local/bin/irb:12:in `<main>`
    irb> for car in @cars
         puts car.reverse
         end
    drof
    yvehc
    adnoh
    atoyot
    #=> ["ford", "chevy", "honda", "toyota"]
    irb> car
    #=> "toyota"
    

    for/in leaves the iterator variable in scope afterwards, while #each doesn’t.

    Personally, I never use ruby’s for/in syntax.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 382k
  • Answers 382k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer I had the same issue and I fix it deleting… May 14, 2026 at 10:24 pm
  • Editorial Team
    Editorial Team added an answer That's definitely a custom job. However, it's basically a UIToolbar… May 14, 2026 at 10:24 pm
  • Editorial Team
    Editorial Team added an answer http://www.appsamuck.com/ may not be all you want but is a… May 14, 2026 at 10:24 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.