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
Ambiguous module resolution causes erroneous name mangling #288
Comments
Oh, that’s interesting! As per the definition of It doesn’t, though, and that might be because it’s both an interface function ( Great find! |
Thanks for finding this! I’ll solve it unless anyone else wants to get their hands dirty :) |
I’m currently working on this. It’s weird. If I drop into a REPL with this and call |
Oh, that’s even weirder... but a good clue. I’ll investigate and see if I can give you some pointers |
I think the problem is line 234 in
Instead it should probably copy the Right now the function that figures out those things is |
If the code uses two modules which have similarly named functions, it may be able to infer the correct one but the name mangling doesn't keep up.
This code has "init"-functions from two modules (Vector2, GLFW) and Carp infers that GLFW is the correct one but produces incorrect C-code:
The error message from C-compiler is
The text was updated successfully, but these errors were encountered: