Code Monkey home page Code Monkey logo

designpatternswebinar's People

Contributors

nesteruk avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

hagudegozaru aimoonchen joydeeps coderx7 grantrostig exh serioussamv yodamaster pekkipo phoenixstar7 manojk16 guoyu07 barisere lopesivan ppngiap qianqian121 worthy-os paicharan mcubrilo p-n-s tomasz0 harshagowda xiuyuma pkumarg borgio amareshkumar nsikanikpoh kb15 binoyjayan kistlin azurecloudmonk adamvm marcindus rajatsahani mxagar eng-eee

designpatternswebinar's Issues

facet-builder example : removing redundant construction of Person objects for each sub-factory

The facet-builder is a nice pattern. However in the example, having the PersonBuilder instantiate an addition Person object for each sub-factory seemed non-intuitive when you just need a single owner at an outer-scope to the fluent evaluation.

I suggest removing Person p; member from PersonBuilder, renaming PersonBuilder to BasePersonBuilder, and adding a new derived class called PersonBuilder that has the Person p; member and passes a reference to its base class in the constructor (the only new method).

As a result only one Person object is constructed, one move-Construct, one destroy of a moved object, and one final destruction of the owning person at program end occurs. Regardless of how many sub-factories are created.

Unless you see a flaw in this approach; I would suggest changing the example in a similar way for the benefit of anyone borrowing the pattern implementation and implementing their own version with many more sub-factories on objects with potentially non-trivial default construction.

Regards.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.