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

How should we enforce that only a single board object exist for onboard implementations? #5

Open
metasoarous opened this issue Mar 26, 2015 · 0 comments
Labels

Comments

@metasoarous
Copy link
Member

One way would be to memoize the get-board function such that it always returns the same object. This could work somewhat similarly for overwire boards, except that the instantiation memoization would also look at :port, or whatever can be used as a unique identifier as to which board is behind the scenes. However, for overwire, it may be possible to write things such that this isn't necessary, if it always looks up state things directly from the board instead of caching :mode values and such.

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

No branches or pull requests

1 participant