Paul Evans

> But this does not work for other libraries that Neovim uses such as libtermkey, which themselves directly call Unibilium internally and do not gain the benefit of Neovim's internal...

See also https://rt.cpan.org/Ticket/Display.html?id=123603

I think at this point that's probably reasonable. mauke hasn't been seen around for a while now so doing something to continue maintaining it would make sense, and best to...

With core-shipped modules, the neatest that can currently be done is probably `List::Util::pairs`: ```perl use List::Util 'pairs'; foreach ( pairs %$hash ) { my ($k, $v) = @$_; ... }...

Having `shift` change its behaviour inside a `forall` block would be kinda weird. But currently I don't see the difference from the tried-and-tested: ```perl while(@list) { my ($x, $y, $x)...

> @leonerd: `while( @list ){ ... }` its great. Could you add this to documentation for `List::Util`? Why? It shouldn't be `List::Util`'s job to teach users basic Perl.

> I thought we could use this in public headers because C++? Ugh; it's `mg_vtable.h`, indeed. Does that still count? Even if we can't use it there, I'd still like...

> @leonerd, Given where we are in our annual production cycle, are you thinking of this for 5.40 or 5.42? Oh it doesn't need to be in 5.40 at all;...

For reference, this behaviour hasn't changed since 5.14: ``` $ eachperl -E 'say $& if "abcde" =~ / ^ a (?: (?: (??{""}) b | bc (*ACCEPT) ) (*THEN) (*FAIL)...

# Aside Thoughts As a total aside, I sometimes feel this a *far* more general and wide-spread naming convention problem across all of Perl, and could be solveable by something...