https://github.com/janbaig/visitor-design-pattern

Implementation and Explanation of the Visitor Design Pattern
https://github.com/janbaig/visitor-design-pattern

design-patterns tutorial visitor-design-pattern

Last synced: 3 days ago
JSON representation

Implementation and Explanation of the Visitor Design Pattern

• Host: GitHub
• URL: https://github.com/janbaig/visitor-design-pattern
• Owner: JanBaig
• Created: 2023-03-07T22:14:13.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-01-22T15:48:18.000Z (10 months ago)
• Last Synced: 2024-01-22T20:03:07.979Z (10 months ago)
• Topics: design-patterns, tutorial, visitor-design-pattern
• Language: C++
• Homepage: https://janbaig.netlify.app/posts/visitor_design_pattern/
• Size: 36.1 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Visitor Design Pattern

### Description

The visitor design pattern is a behavioural design pattern that allows for the separation of algorithms from the objects on which they operate. 

Adding new methods within subclasses works fine if the program being developed isn't complex - simply add the methods to each of the individual subclasses. For example, if we have an Animal parent class, each of the Animal subclasses may need to implement a `makeSounds()` method. However, when our codebase consists of dozens of new methods to be implemented for dozens of subclasses, the code within each subclass becomes cluttered and often becomes difficult to maintain.

The visitor design pattern solves this problem. It allows for the addition of methods into subclasses *without modifying* the existing subclasses themselves. So, if we need all of our subclasses to implement the `makeSound()` method, instead of _individually_ going into each subclass and adding it, we can instead couple all the `makeSound()` implementations for each subclass in one place. That way we only need to visit one section in our code and modify that section alone - effectively resulting in all subclasses having implementations of `makeSound()` without having to visit each and every subclass separately.

> Check out a [blog](https://janbaig.netlify.app/posts/visitor_design_pattern/) I've written explaining the concept in far greater detail if you'd like to learn more! 👾