Why generated adaptors/proxies don't have default and move constructor?

[pawelwod]

I'm currently forced to store new objects in std::uint_ptr which in turn are stored in std::vector. If there would be move constructor available then it would enable std::vector<foo_adaptor> instead of std::vector<std::uint_ptr<foo_adaptor>>. Additionally if there would be default constructor available then separating construction from initialization would be possible.

Why generated adaptors don't have default and move constructor?

I know the obvious answear, but is there any obstacle in changing library to hold pointers (maybe shared ones) instead of references?

[sangelovic]

1. What is std::uint_ptr? I know only std::uintptr_t. And that surely isn't a template, so this would be a syntax error: std::uintptr_t<foo_adaptor>

2. Generated adaptors and proxies do have a move constructor and move assignment operator. Look here for an example.

3. Generated adaptors and proxies don't have a default c-tor by design. They need an IObject or IProxy in order to be considered valid and fully constructed instances. But, they are not intended to be used by you as a client directly. Instead, use ProxyInterfaces and AdaptorInterfaces and place the generated classes as their template arguments.

4. We don't have a concept of empty/invalid ProxyInterfaces and AdaptorInterfaces instances. That would start complicating the design.

5. I'd say separating construction and initialization is not what I'd want. We have constructors to actually initialize the instance to be ready for use.

6. to hold pointers (maybe shared ones) instead of references?

What exactly do you mean? Can you provide an example?

7. This is more a discussion thread than an issue. Please use GitHub Discussion feature for that in the future...