-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Bessel and Airy functions should not silently convert BigFloat to Float64 #11512
Comments
Yes, I was planning to file an issue for this myself. I think the current behavior (in Possibly this code dates from the days when the only fp types were Float32 and Float64? For Float32, of course, it is perfectly appropriate to convert to Float64, compute the special function, and then round back to Float64. |
Similarly for some of the other special functions. |
+1 |
…type) We implement an explicit type checking and disable Complex{BigInt} and Complex{BigFloat}. Currently only do for Bessel and Airy function.
…type) We implement an explicit type checking and disable Complex{BigInt} and Complex{BigFloat}. Currently only do for Bessel and Airy function.
…type) We implement an explicit type checking and disable Complex{BigInt} and Complex{BigFloat}. Currently only do for Bessel and Airy function.
…type) We implement an explicit type checking and disable Complex{BigInt} and Complex{BigFloat}. Currently only do for Bessel and Airy function.
Hi,
Super huge fan of the Julia language. I'm a developer at ApproxFun.jl and have been implementing some function approximation routines in extended precision. It looks like the Bessel and Airy functions don't have mpfr routines for
Complex{BigFloat}
, yet Julia gives results fromfloat64
ed values. Until an algorithm is implemented/wrapped, maybe an error/warning message is more appropriate?The text was updated successfully, but these errors were encountered: