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 824629
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T03:07:35+00:00 2026-05-15T03:07:35+00:00

I have a question regarding the ||= statement in ruby and this is of

  • 0

I have a question regarding the ||= statement in ruby and this is of particular interest to me as I’m using it to write to memcache. What I’m wondering is, does ||= check the receiver first to see if it’s set before calling that setter, or is it literally an alias to x = x || y

This wouldn’t really matter in the case of a normal variable but using something like:

CACHE[:some_key] ||= "Some String"

could possibly do a memcache write which is more expensive than a simple variable set. I couldn’t find anything about ||= in the ruby api oddly enough so I haven’t been able to answer this myself.

Of course I know that:

CACHE[:some_key] = "Some String" if CACHE[:some_key].nil?

would achieve this, I’m just looking for the most terse syntax.

  • 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-15T03:07:36+00:00Added an answer on May 15, 2026 at 3:07 am

    This is extremely easy to test:

    class MyCache
      def initialize
        @hash = {}
      end
    
      def []=(key, value)
        puts "Cache key '#{key}' written"
        @hash[key] = value
      end
    
      def [](key)
        puts "Cache key '#{key}' read"
        @hash[key]
      end
    end
    

    Now simply try the ||= syntax:

    cache = MyCache.new
    cache["my key"] ||= "my value"  # cache value was nil (unset)
    # Cache key 'my key' read
    # Cache key 'my key' written
    
    cache["my key"] ||= "my value"  # cache value is already set
    # Cache key 'my key' read
    

    So we can conclude that no assignment takes place if the cache key already exists.

    The following extract from the Rubyspec shows that this is by design and should not be dependent on the Ruby implementation:

    describe "Conditional operator assignment 'obj.meth op= expr'" do
      # ...
      it "may not assign at all, depending on the truthiness of lhs" do
        m = mock("object")
        m.should_receive(:foo).and_return(:truthy)
        m.should_not_receive(:foo=)
        m.foo ||= 42
    
        m.should_receive(:bar).and_return(false)
        m.should_not_receive(:bar=)
        m.bar &&= 42
      end
      # ...
    end
    

    In the same file, there is a similar spec for [] and []= that mandates identical behaviour.

    Although the Rubyspec is still a work in progress, it has become clear that the major Ruby implementation projects intend to comply with it.

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

Sidebar

Ask A Question

Stats

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

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

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

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

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer From a command line, the Microsoft-provided solution is secedit. AppDeploy… May 15, 2026 at 10:43 am
  • Editorial Team
    Editorial Team added an answer You should add <base href="http://www.abc.com/original/path"> in the head section of… May 15, 2026 at 10:43 am
  • Editorial Team
    Editorial Team added an answer The obvious error in your program is that you are… May 15, 2026 at 10:43 am

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.