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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T13:58:10+00:00 2026-05-21T13:58:10+00:00

Can someone explain the behavior of the following def iterate return yield return end

  • 0

Can someone explain the behavior of the following

def iterate
  return yield
  return "end of iterate"
end

def test_iterate
  assert_equal( "end of iterate",  iterate { return "end of block" } )
  assert_equal( "end of block",  iterate { "end of block" } )
end

I understand that Procs ( Which is what blocks are ) should return within the scope they are called. ( Unlike lambdas ) With this in mind, shouldn’t both calls in the tests return “end of block”?

This test passes on ‘ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]’ ( OSX 10.6.7 )

  • 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-21T13:58:11+00:00Added an answer on May 21, 2026 at 1:58 pm

    The return keyword returns from the lexicaly enclosing method. That is, *test_iterate*.

    To return a certain value from a block in a dynamically scoped fashion, you should use the break keyword instead.

    In your case:

    iterate { break("end of block") }
    

    The test will fail. because the second return statement of the iterate method will never run.

    The intended semantics should be accomplished by using exceptions:

    def iterate
      return yield
      rescue :exception
        return "end of iterate"
    end
    
    def test_iterate
      assert_equal( "end of iterate",  iterate { raise :exception } )
      assert_equal( "end of block",  iterate { "end of block" } )
    end
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Can someone explain the following behaviour: class derivedset1(frozenset): def __new__(cls,*args): return frozenset.__new__(cls,args) class derivedset2(set):
Can someone explain the following behavior? Specifically, why does the function return a different
Can someone explain the following strange behavior? I run the following program on a
Hopefully someone can explain some odd behavior I've encountered with jQuery. The following script
Can someone explain the following behavior in Java sockets: The general idea is this:
I've noticed an unusual behavior when developing using javascript, can someone explain that to
Can someone explain me the behaviour of the following line in VB Return Not
Can someone explain to me the following behavior on x64 platform: If I call
I'm not understanding this behavior. Maybe someone can explain to me why my current
Can someone explain the following behaviour (I'm using Visual Studio 2010). header: #pragma once

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.