-
Notifications
You must be signed in to change notification settings - Fork 59
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
Thread safety #1310
Comments
Hm, I think one can assume that nothing is thread-safe (due to caching or precision handling). Maybe we should mention this somewhere. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it would be nice if the documentation mentioned that some of the functions are not thread safe, even when called with completely unrelated parameters (for example due to
setprecision(...)
, and maybe also due to caching). I don't know whether by default people would assume that the library is thread safe in any way, but given that there's a warning about one specific function here, it might be a natural guess.The text was updated successfully, but these errors were encountered: