Elizabeth Mattijsen via RT wrote: >As with #126941, commit f6091476486d29c8886d gives this a slightly >better error message, at least until 6.c.
Providing any error here, rather than a wrong answer, resolves this issue. At least it does so for the cases with a non-zero lhs, for which the correct answer can't be represented. In the exception where the lhs is zero, formerly shift distances up to ((1 +< 64) - 1) were accepted, and it's a shame to reduce that range. But either way that range being limited is LTA in a manner exactly akin to [perl #126941]. That ought to be addressed as an extension of that ticket or as a separate issue. Since you've raised the question of pre-xmas vs post-xmas, I think the only one of these bit-shift tickets that could possibly be a pre-xmas priority is [perl #126942]. Not because it has any deep implications, but just because the lower end of its misbehaviour is reachable with reasonable inputs that are fairly likely to arise in substantive programs. -zefram
