Open jodavies opened 4 years ago
The problem here is that the part ((ep)) is something that gets worked out because you could have put here also $ expressions. Hence it becomes ((0)), and this will always match. It would be a matter of very specific special cases to be inserted in rather complicated code to try to avoid it, and then maybe somebody else may complain that they would have it the old way. It is more an extremely tricky point rather than a bug.
Hello,
The following code produces an incorrectly split argument.
This breaks a procedure which automatically determines a power limit based on what appears in the expression.
I suppose this is a consequence of
((ep))
going though normalization (the output is the same asSplitArg ((0))
). I have coded around it, but thought I should mention it here.Thanks, Josh.