Front page | perl.perl5.porters |
Postings from April 2016
On Mon Apr 11 00:41:51 2016, kentfredric wrote: > There's been a lot of idle chat about this, but not any real > commitment to a resolution either to block, or to vocally state an > intent to release with a known broken and significant module. I wonder if either: a) Scope::Upper should be maintained in core, since it's tied so much to the implementation, or b) we should provide an API so that tools like Scope::Upper (and perhaps Coro) can be written without implmentation changes breaking them Tony --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=127875Thread Next