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

Separate memblock and vector functionality #42

Closed
JarrettBillingsley opened this issue May 27, 2012 · 1 comment
Closed

Separate memblock and vector functionality #42

JarrettBillingsley opened this issue May 27, 2012 · 1 comment

Comments

@JarrettBillingsley
Copy link
Owner

The more I think about it, the more sense it makes to keep memblocks as a basic blob of bytes. Having to check that memblocks are of the appropriate type is awkward and annoying. Really, the vector functionality (treating them as mathematical vectors of numbers) should be moved into a separate object using a memblock to back it, much like StringBuffer uses a memblock as its backing data store.

@JarrettBillingsley
Copy link
Owner Author

Closed in 4b4f71f

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