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

Planning: version number incompatibilities between libraries #37

Open
LB-- opened this issue May 11, 2016 · 1 comment
Open

Planning: version number incompatibilities between libraries #37

LB-- opened this issue May 11, 2016 · 1 comment

Comments

@LB--
Copy link
Member

LB-- commented May 11, 2016

Since some basic containers will be separate libraries and independently versioned, it is possible for code using one version to need to communicate with code using another version.

In general this can be solved with duck typing and converting between versions as needed.

Needs more thought...

@LB-- LB-- self-assigned this May 11, 2016
@LB-- LB-- added the planning label May 11, 2016
@LB--
Copy link
Member Author

LB-- commented May 14, 2016

Dependency injection is a really good idea, and perhaps reverse dependency injection may also work in some cases. Both would require duck typing...

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

1 participant