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

  • SEARCH
  • Home
  • 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 8693375
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T00:31:57+00:00 2026-06-13T00:31:57+00:00

I am new to Ruby and I did the following: c = {} #

  • 0

I am new to Ruby and I did the following:

c = {}
# Some code in the middle
c['a'] = c['a'] or 0

Now I would expect this to work like this: if c['a'] is nil, then c['a'] or 0 would return 0. So the value of c['a'] should be 0.

However the value of c['a'] is nil. Why does this happen?

  • 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-06-13T00:31:58+00:00Added an answer on June 13, 2026 at 12:31 am

    or is not the same as || in Ruby. What you have becomes grouped like so:

    (c['a'] = c['a']) or 0
    

    which will basically do nothing. You should use || instead:

    c['a'] = c['a'] || 0
    

    or simply:

    c['a'] ||= 0
    

    Note that and/&& has the same behavior as or/||.

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

Sidebar

Related Questions

Im new to ruby, wrote this code and works but i know is not
I'm a bit new to ruby and test/unit so this may seem like a
I was kidding with metaprogramming in Ruby and I did this code: class Class
I'm fairly new to ruby and I've got a hash that looks like so:
With my Ruby script: imap = Net::IMAP.new('imap.gmail.com') imap.login(some_email@host.com, password) I get the following exception:
I'm getting a strange nil problem with the following code. The view (part of
I am relatively new to ruby on rails, so this question might be easy.
I am very new to Ruby on Rails and I was following the Railstutorial
I am quite new to Ruby and Ruby on Rails. While following a Ruby
I am following this routing tutorial for Ruby on Rails: http://guides.rubyonrails.org/routing.html It says that

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.