StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13534397
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-23T18:48:09.413
FavoriteCount
0
LastActivityDate
2015-01-05T10:00:40.180
LastEditDate
2015-01-05T10:00:40.180
LastEditorUserId
2767755
OwnerUserId
429758
ParentId
13533439
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
What does <code>expect { |b| 5.tap(&b) }.to yield_control</code> do? It is expecting that the code given in the block invokes <code>yield</code> statement. The code given in the block (viz. <code>{ |b| 5.tap(&b) }</code>) calls the <a href="http://ruby-doc.org/core-1.9.3/Object.html#method-i-tap" rel="nofollow">ruby 1.9 tap method</a> which has a <code>yield</code> statement within it's implementation. So the statement is effectively asserting that ruby 1.9's tap method has a <code>yield</code> statement. :-) To better understand this statement, try the following code example: <code>order.rb</code> file <pre><code>class Order end </code></pre> <code>order_spec.rb</code> file <pre><code>require 'rspec-expectations' require './order' describe Order do it "should yield regardless of yielded args" do expect { |b| 5.tap(&b);puts "The value of b is #{b.inspect}" }.to yield_control end end </code></pre> Output from executing the spec: <pre><code>$ rspec yield_spec.rb Order The value of b is #<RSpec::Matchers::BuiltIn::YieldProbe:0x000001008745f0 @used=true, @num_yields=1, @yielded_args=[[5]]> should yield regardless of yielded args Finished in 0.01028 seconds 1 example, 0 failures </code></pre> To understand the other lines in the yielding section, similarly include the <code>expect</code> statements in the spec file as follows: <pre><code> it "should yield with no args" do expect { |b| Order.yield_if_true(true, &b) }.to yield_with_no_args end it "should yield with 5 args" do expect { |b| 5.tap(&b) }.to yield_with_args(5) end it "should yield with integer args" do expect { |b| 5.tap(&b) }.to yield_with_args(Fixnum) end it "should yield with string args" do expect { |b| "a string".tap(&b) }.to yield_with_args(/str/) end it "should yield 1,2,3 successively" do expect { |b| [1, 2, 3].each(&b) }.to yield_successive_args(1, 2, 3) end it "should yield ([:a,1], [:b,2]) successively" do expect { |b| { :a => 1, :b => 2 }.each(&b) }.to yield_successive_args([:a, 1], [:b, 2]) end </code></pre> Note: The <code>yield_if_true</code> method used in the second line seems to be removed from where it was originally defined; I got it go work by adding it into the Order class as follows: <pre><code>class Order def self.yield_if_true(flag) yield if flag end end </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POwhat does this line of code "expect { |b| 5.tap(&b) }.to yield_control" implementing functionally?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USArup Rakshit
UserOwnerUserId
1. USPrakash Murthy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POwhat does this line of code "expect { |b| 5.tap(&b) }.to yield_control" implementing functionally?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.