Databases
StackOverflow2013
Postsdbo
POSome clarification on rvalue references
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSome clarification on rvalue references
    primarykey
    data
    text
    <p>First: where are <code>std::move</code> and <code>std::forward</code> defined? I know what they do, but I can't find proof that any standard header is required to include them. In gcc44 sometimes <code>std::move</code> is available, and sometimes its not, so a definitive include directive would be useful.</p> <p>When implementing move semantics, the source is presumably left in an undefined state. Should this state necessarily be a valid state for the object? Obviously, you need to be able to call the object's destructor, and be able to assign to it by whatever means the class exposes. But should other operations be valid? I suppose what I'm asking is, if your class guarantees certain invariants, should you strive to enforce those invariants when the user has said they don't care about them anymore?</p> <p>Next: when you don't care about move semantics, are there any limitations that would cause a non-const reference to be preferred over an rvalue reference when dealing with function parameters? <code>void function(T&amp;);</code> over <code>void function(T&amp;&amp;);</code> From a caller's perspective, being able to pass functions temporary values is occasionally useful, so it seems as though one should grant that option whenever it is feasible to do so. And rvalue references are themselves lvalues, so you can't inadvertently call a move-constructor instead of a copy-constructor, or something like that. I don't see a downside, but I'm sure there is one.</p> <p>Which brings me to my final question. You still can not bind temporaries to non-const references. But you can bind them to non-const rvalue references. And you can then pass along that reference as a non-const reference in another function.</p> <pre><code>void function1(int&amp; r) { r++; } void function2(int&amp;&amp; r) { function1(r); } int main() { function1(5); //bad function2(5); //good } </code></pre> <p>Besides the fact that it doesn't do anything, is there anything wrong with that code? My gut says of course not, since changing rvalue references is kind of the whole point to their existence. And if the passed value is legitimately const, the compiler will catch it and yell at you. But by all appearances, this is a runaround of a mechanism that was presumably put in place for a reason, so I'd just like confirmation that I'm not doing anything foolish.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJohannes Schaub - litb
    1. USDennis Zickefoose
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSome clarification on rvalue references
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSome clarification on rvalue references
      1. USDmitry Yudakov
      1. VTFavorite
    3. VO
      singulars
      1. POSome clarification on rvalue references
      1. This table or related slice is empty.
      1. VTUpMod
    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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload