Copying Rob's one-liner into my system gives yet another answer:

-1+1.22464679914735e-16i

Using perl -v, my perl is "

This is perl 5, version 32, subversion 1 (v5.32.1) built for x86_64-linux-gnu-thread-multi

That's hinting at something, but I'm not quite sure what.

Tried (and hopefully succeeded) in fixing the formatting, so my reply isn't in my sig.

Copying Rob's one-liner into my system gives yet another answer:
-1+1.22464679914735e-16i

That's the same result as the OP got.
The difference is that perl's print function rounded the final 2 digits away, whereas Raku's didn't.
Now that I'm back home, I can see the same with perl on Ubuntu-20.04.
The figure that I reported came from Windows, so there's a discrepancy in the underlying C libraries.

C:\>perl -le "printf '%a',  1.2246467991473532e-16;
0x1.1a62633145c07p-53
C:\>perl -le "printf '%a',  1.2246063538223773e-16;
0x1.1a6p-53
[download]

The latter (which is what windows is reporting) is suspiciously truncated.

With the MPC library, the given inputs produce a result of -1+2.8954204500590832e-16.

Cheers,
Rob

I'd not expect perl to return exactly zero to sin(pi) and I don't get it, but 1.22464679914735e-16

The reliance on the sine and cosine trig functions can be seen at https://www.math.toronto.edu/mathnet/questionCorner/complexexp.html.
For the case under consideration in this thread, the imaginary component should be sin(3.1415926535897931 * log(2.7182818284590451))
log(2.7182818284590451) is calculated to be exactly 1 and, as already noted, sin(3.1415926535897931) is calculated to be 1.2246467991473532e-16.

I don't know how the MPC library is coming up with 2.8954204500590832e-16, but I'm about to ask them about that, and I'll update this post when I get the answer.

UPDATE: I've changed my mind - the value returned for these inputs is very sensitive to minute changes in the evaluation of those inputs. For example:

sisyphus@sisyphus5-desktop:~$ perl -MMath::Complex -E "say sin(pi * 1)
+;"
1.22464679914735e-16
sisyphus@sisyphus5-desktop:~$ perl -MMath::Complex -E "say sin(pi * 0.
+99999999999999994);"
5.66553889764798e-16
[download]

I don't see much point in investigating further when such a minute alteration to the arguments can make such a large relative difference, especially when we consider that the absolute difference is so minute.

Cheers,
Rob

There may be a world where a language can do identity / symbol math - indeed there are cpan packages for this kind of thing. But core Raku does not attempt to do that. Raku is (fortunately) pretty simplistic: you get Ints, Rats and Nums (well and Complex but that's another topic). This aligns to mathematics number spaces Integers, Rational and Irrational numbers. Some operations (eg. sqrt(2)) will make an irrational number. Without symbolic math, you lose a little precision in any machine with finite word size and cannot fully restore the initial state with a round trip. Rounding can hide this.

> my $t=sqrt(2)
1.4142135623730951
> $t ** 2
2.0000000000000004
[download]

sooooo You are plumbing the edges of IEEE754 here ... and very small numbers are subject to all kinds of influences ... here is a good write up ...https://randomascii.wordpress.com/2013/07/16/floating-point-determinism/ Back in the day many FPUs did random seed guess for division/sqrt ... even if that practice has become standardised to make the result deterministic (every pass is the same), it certainly will not require each FPU design to guess the same seed. And this ignores the fact that FPU designers will often shortcut full IEEE754 to save on transistors, various compiler settings. Not to rule out frequent chip logic design errors that do not get caught since the test sw will judge any of the near '0' as zero.