Note that there are some explanatory texts on larger screens.

plurals
  1. USBrett Rossier
    primarykey
    data
    text
    plurals
    1. CORead up in the Standard:n1905, Temporary Objects: "There are two contexts in which temporaries are destroyed at a different point than the end of the full-expression. The first context is when a default constructor is called to initialize an element of an array...The second...when a reference is bound to a temporary. The temporary to which the reference is bound or the temporary that is the complete object of a subobject to which the reference is bound persists for the lifetime of the reference except as specified below..." Not sure if joint_view falls under the exceptions to that rule or not.
      singulars
    2. COStreamline your data collection as much as possible. Incoming e-mails should be on an e-mail server somewhere, so you should be able to pull info out of it. Phone calls are probably logged in a PBX system, and if it's a digital system you should be able to get info out of it. SMS... not sure how you're going to log that info unless you've got a system sitting between the two people texting. If you do, it should have info that you could pull out. All three cases would require someone know how to get into each system's data, and figure out how to get it to the data mart.
      singulars
    3. COChewed on what you said for a bit... I added another test case and it worked, and I understand why it worked, but I'm still a little lost, so please bear with me. Yes I was creating temps, but wrapping them in smart pointers, and giving those to the fusion container, itself a temp. But before the container goes out of scope, I add another ptr-wrapped temp to it, producing a `joint_view` that holds refs to... my smart pointers (my assumption)? Or does it have refs to the elements behind my smart pointers? If it strips off my pointers, then I understand my objects going out of scope.
      singulars
 

Querying!

 
Guidance

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