forked from icaven/glm
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fast sqrt functions ambiguity #215
Comments
Hi, With GLM 0.9.5, if you use glm::lowp_float32 dist = glm::distance(glm::lowp_f32vec2(destination.x, destination.z), glm::lowp_f32vec2(loc.x, loc.z)); you will access the same fast path. glm::fastDistance should probably be fixed as well. Thanks, |
It's good to know. Thank you for help! |
Groovounet
pushed a commit
that referenced
this issue
Jun 19, 2014
This issue is fixed in GLM 0.9.5 branch and for GLM 0.9.5.4 release. Thanks for contributing, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello.
I encountered difficulties using fast sqrt functions (GLM_GTX_fast_square_root extension).
The problem is ambiguity between the functions, that only differ in returning type, which (the returning type) is genType or genType::value_type.
The example:
glm::mediump_float32 dist = glm::fastDistance(glm::mediump_f32vec2(destination.x, destination.z), glm::mediump_f32vec2(loc.x, loc.z));
Above line generates error:
more than one instance of overloaded function "glm::fastDistance" matches the argument list:
function template "genType::value_type glm::fastDistance(const genType &x, const genType &y)"
function template "genType glm::fastDistance(const genType &x, const genType &y)"
argument types are: (glm::mediump_f32vec2, glm::mediump_f32vec2)
I believe it is a GLM bug. Is there any known workaround solution for this?
The text was updated successfully, but these errors were encountered: