Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor examples with Readme and more real-world cases #18

Open
abishekaditya opened this issue May 2, 2020 · 1 comment
Open

Refactor examples with Readme and more real-world cases #18

abishekaditya opened this issue May 2, 2020 · 1 comment

Comments

@abishekaditya
Copy link
Owner

A strategy pattern that makes ducks quack is less useful than that which uses an actual strategy to help the developer (like say, a sorting function that changes implementation based on number of elements). The readme should also be there as an introduction to the need for the pattern itself, as well as maybe some good quality (subjective) external references and links

@FunkyMonk8111
Copy link
Contributor

How would you implement this? I found this article, would this work? Inheriting IList or ICollection from the Duck class? https://newdevsguide.com/2022/10/09/understanding-dotnet-collection-interfaces/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants