Robert Eisele

Why not setting on Svelte then if performance is an issue?

Oh, that are good findings! Thanks a lot for the ticket and notifying me about #804! I'll look into this. About the last point, it's a mere philosophical question if...

Okay, I added a new branch "infinity": https://github.com/infusion/Complex.js/commit/f06449fef848cf7dd4fd0aba3e48c31c054dcf94 I added a new symbol Complex.Infinity, which sets real and imaginary part to infinity. This symbol is returned for inv(0), div(z, 0)...

Hm, yep I thought the same way and I think a real infinity should stay real. However, wolframalpha decided (maybe for the same reason) to print complex infinity for any...

Okay, there is an update in infinity branch. - `isFinite` was added - 0/0 is now complex infinity as well, even if it's not defined. Let's see if we can...

The purpose is to keep the sign of each Infinity.

As long as you're in the MAX_SAFE_INTEGER range, the pow function has no numerical problems. For the log, there might be a problem, but as it is floor'ed, the problem...

Yep, performance is also a concern to me when it comes to switching to BigInt. The code is refactored maybe a million times to come up with a performant implementation...

As far as I know, in some engines Math.abs is faster since they mark Math.abs as not changed (by a polyfill for example) and link the symbol "Math.abs" directly to...

Comparing `re` and `im` is done here as well, but not in a `==` manner but comparing against a rounding-error ignoring small epsilon. And since `Inf-Inf =Inf > eps` it...