[Perl/perl5] e1c331: t/op/taint.t: Slight modernisation to use builtin:...

  Branch: refs/heads/blead
  Home:   https://github.com/Perl/perl5
  Commit: e1c331b1f437e2a5c7ffe45cacc7cf8a41dea8c1
      https://github.com/Perl/perl5/commit/e1c331b1f437e2a5c7ffe45cacc7cf8a41dea8c1
  Author: Paul "LeoNerd" Evans <[email protected]>
  Date:   2026-08-20 (Thu, 20 Aug 2026)

  Changed paths:
    M t/op/taint.t

  Log Message:
  -----------
  t/op/taint.t: Slight modernisation to use builtin::is_tainted

We've had builtin::is_tainted since v5.36 so there's really no need for
it to use the old `eval { join ... }` trick any more.


  Commit: fd584474cf36982e2f2ef85b042ea51bb02fffaa
      https://github.com/Perl/perl5/commit/fd584474cf36982e2f2ef85b042ea51bb02fffaa
  Author: Paul "LeoNerd" Evans <[email protected]>
  Date:   2026-08-20 (Thu, 20 Aug 2026)

  Changed paths:
    M sv.c
    M t/op/taint.t

  Log Message:
  -----------
  newSVsv(): Ensure taint propagation on IVs and NVs

Previously, the `return dsv` meant it skipped the `SvTAINTED(ssv)` check
later on, meaning that tainted numbers that don't contain stringy parts
would lose that taint annotation.

Technically this code also ensures tainted RVs and booleans will
propagate correctly, but I could not work out how to generate such a
value to test it ;)

This came up while testing the related "value magic" which uses similar
annotation code, and I found this was missing there too.


Compare: https://github.com/Perl/perl5/compare/fa0028418233...fd584474cf36

To unsubscribe from these emails, change your notification settings at https://github.com/Perl/perl5/settings/notifications