You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now call f. If the compiler has chosen to inline "_" in the definition of f, it hopes to get the first definition of _. Unfortunately, both definitions of "*" have the same hash code in the case of Complex I, and if we get the second, mayhem will result.
For a real example, see the initial version of reciprocal in sal_complex.as.
The text was updated successfully, but these errors were encountered:
Why is this a particular problem with inlining? If the semantics of *: (T, %) -> % and *: (I, %) -> % is different for T=I, then that is problematic anyway. I'm not aware of the fact that in Aldor one can have two different actions (I, %) -> % that are denoted by the same identifier *.
.. this comes from investingating issues with Complex Integer.
Start with a domain like:
Now inherit these definitions...
All good so far.
Now call f. If the compiler has chosen to inline "_" in the definition of f, it hopes to get the first definition of _. Unfortunately, both definitions of "*" have the same hash code in the case of Complex I, and if we get the second, mayhem will result.
For a real example, see the initial version of reciprocal in sal_complex.as.
The text was updated successfully, but these errors were encountered: