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

Restructure #42

Open
richardstartin opened this issue Jun 6, 2018 · 3 comments
Open

Restructure #42

richardstartin opened this issue Jun 6, 2018 · 3 comments

Comments

@richardstartin
Copy link

I am experimenting with this library and the project panama vector API. In my fork, I have restructured the project slightly to make it easier to run benchmarks on a branch. The changes are all related to moving code around and bumping the Java language level. Would these changes be useful? If so, how could it be validated that they don't break your release process?

@lemire
Copy link
Member

lemire commented Jun 6, 2018

I think this would be interesting. Why would it break the release process?

@richardstartin
Copy link
Author

I just remember there being complexities in RoaringBitmap when a similar transformation was made. The reason I wanted to make the changes was to make it easier to add new benchmarks. The sibling project should still release as JavaFastPFOR but it's hard to verify that this will work.

@lemire
Copy link
Member

lemire commented Jun 6, 2018

I might end up swearing a lot, true. But that does not mean it is not worth doing.

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

No branches or pull requests

2 participants