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

ComputeFunctions have the capability to corrupt memory when used recursively #36

Open
Speiger opened this issue Jul 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Speiger
Copy link
Owner

Speiger commented Jul 17, 2024

Technically Java doesn't support this functionality but i really like the ability to do so.

int newValue = mappingFunction.applyAsInt(key, getDefaultReturnValue());

The compute function is capable to be used recursively and technically it can end well if it is in small amounts.
There are 0 checks in place to ensure that corruption happend or to prevent it from happening.

While this is not a bug at the moment and just undefined behavior i would like to make this defined behavior.

@Speiger Speiger added the enhancement New feature or request label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant