StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9883008
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-03-27T03:28:48.737
FavoriteCount
0
LastActivityDate
2012-03-27T13:08:49.657
LastEditDate
2012-03-27T13:08:49.657
LastEditorUserId
576911
OwnerUserId
576911
ParentId
9882871
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Guideline: Do not overload: <pre><code>template <typename T> void f(T&) {} template <typename T> void f(T&&) {} </code></pre> Reason: There is a special template deduction rule for the pattern: <pre><code>template <typename T> void f(T&&) {} </code></pre> This rule exists in order to enable so called "perfect forwarding". It helps things like <code>bind</code> and <code>make_shared</code> forward their arguments perfectly, preserving both cv-qualifiers and "value category" (lvalue/rvalue-ness). This special rule says that when <code>f(T&&)</code> is called with an lvalue parameter (e.g. <code>int</code>), that T gets deduced as an lvalue reference (e.g. <code>int&</code>) instead of <code>int</code>. And an rvalue reference to lvalue reference to int collapses down to just lvalue reference to int. I.e. <pre><code>f(x) </code></pre> calls <pre><code>f<int&>(int& && x); </code></pre> which simplifies to: <pre><code>f<int&>(int& x); </code></pre> Edit <del>This is not more or less specialized than <code>f<int>(int&)</code>.</del> Thanks to Johannes Schaub for the correction (see comments). Solution: You can do whatever you want with the single function: <pre><code>template <typename T> void f(T&&) {} </code></pre> If <code>T</code> deduces as an lvalue reference, do whatever you wanted to do in your first overload, otherwise do whatever you wanted to do in your second overload: <pre><code>template <class T> void f_imp(T&, std::true_type) {std::cout << "lvalue\n";} template <class T> void f_imp(T&&, std::false_type) {std::cout << "rvalue\n";} template <typename T> void f(T&& x) { f_imp(std::forward<T>(x), std::is_lvalue_reference<T>()); } </code></pre> And use <code>std::forward</code> to perfectly forward <code>x</code> to the implementation-detail function.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOverloaded function templates with reference parameters
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USHoward Hinnant
UserOwnerUserId
1. USHoward Hinnant
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COwhile it is indeed correct to point out that one should not write such an overload, from memory i remember that the first template is intended to be more specialized (that wasnt always the case in c++0x drafts), and the wording appears to reflect that intent.
 singulars
 PostPostId
 PO
 UserUserId
 USJohannes Schaub - litb
2. CO@JohannesSchaub-litb: Thanks, I've corrected my answer per your comment.
 singulars
 PostPostId
 PO
 UserUserId
 USHoward Hinnant

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.