You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a consequence of #186 (which itself was a consequence of #128). I came up with a (possibly contrived) issue with the latest version of our constructor:
#include<https://raw.githubusercontent.com/jbcoe/value_types/main/indirect.h>structNode {
Node() = default; //ctor 1Node(xyz::indirect<Node>& parent) {} //ctor 2
};
voidf() {
xyz::indirect<Node> root;
xyz::indirect<Node> child(root); //This will call the copy constructor of indirect and not the ctor 2 of Node
}
I know that in #159, I was complaining about the exactly opposite behavior that I am complaining about now. I am not sure what the desired behavior is. Should xyz::indirect<Node> child(root); call the copy-constructor of indirect or ctor 2 of Node?
The text was updated successfully, but these errors were encountered:
This issue is a consequence of #186 (which itself was a consequence of #128). I came up with a (possibly contrived) issue with the latest version of our constructor:
I know that in #159, I was complaining about the exactly opposite behavior that I am complaining about now. I am not sure what the desired behavior is. Should
xyz::indirect<Node> child(root);
call the copy-constructor ofindirect
orctor 2
ofNode
?The text was updated successfully, but these errors were encountered: