0

With a healthy dose of fear for reinventing the wheel - im looking for a generic template for a proxy like object that will help me customize the constructor - a very basic and unfinished sketch look like this:

template<class T>
struct proxy {
  proxy( ? ) {<customized init of elem_ - possible two-phase calling init(), etc. >}
  T& operator*() {return elem_;}
private:
  T elem_;
};

Normally you would implement different access mechanics, etc., etc. which becomes easy to get wrong / or just not very future-proof.

In this case i just need to customize the construction of the object (which can't be copied and is the reason why in this case, such a proxy would be helpfull). Though often for proxy pattern it is the access that is customized. In a pinch, a "lazy construction template" would also solve it.

darune
  • 10,480
  • 2
  • 24
  • 62
  • 1
    What's the advantage over adding an additional constructor? – super Apr 02 '19 at 09:24
  • 1
    @super OP probably cannot change the definition of that type. – Quentin Apr 02 '19 at 09:24
  • 1
    Does your custom "initialization" need to mutate the object after it is actually initialized, as you wrote? Otherwise, C++17's copy elision makes a plain factory function work just fine. – Quentin Apr 02 '19 at 09:27
  • @Quentin it does mutate - so cannot 'exploit' copy elision. – darune Apr 02 '19 at 10:05

0 Answers0