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

Remove the ViewExecutor artificial size limit #100

Merged

Conversation

carterkozak
Copy link
Contributor

Unlike the previous implementations, EnhancedViewExecutor stores
state in a 64-bit integer, allowing both the pool and queue
sizes to use full integers.

There's not any reason to create an executor with more than 32k
active tasks, however the builder uses the int type so it's nice
to allow Integer.MAX_VALUE to have effectively the same impact
as Short.MAX_VALUE and rely on the compiler for input validation.

Unlike the previous implementations, EnhancedViewExecutor stores
state in a 64-bit integer, allowing both the pool and queue
sizes to use full integers.

There's not any reason to create an executor with more than 32k
active tasks, however the builder uses the `int` type so it's nice
to allow `Integer.MAX_VALUE` to have effectively the same impact
as `Short.MAX_VALUE` and rely on the compiler for input validation.
@carterkozak
Copy link
Contributor Author

Very low priority, I just realized I should have removed the cast and assert when I removed the old ViewExecutor implementations.

@dmlloyd dmlloyd merged commit d2c9a92 into jbossas:master May 3, 2021
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

Successfully merging this pull request may close these issues.

None yet

2 participants