gvim writes:
The original request was for a pointer to any definitive list of
edge cases for smart match breakage,
There isn't such a list -- its experimental nature means anything
might change. P5P doesn't have consensus, and no decision has been made
on what's going to happen.
There are
On 2013-06-14 09:11, Smylers wrote:
There isn't such a list -- its experimental nature means anything
might change. P5P doesn't have consensus, and no decision has been
made
on what's going to happen.
There are some on P5P suggesting that smartmatch is so broken it
should
be removed
A lot of? Are people really using this in production code now?
Sent from my iPhone
On 14 Jun 2013, at 09:32, jason ja...@ukfsn.org wrote:
On 2013-06-14 09:11, Smylers wrote:
There isn't such a list -- its experimental nature means anything
might change. P5P doesn't have consensus, and no
Presumably CPAN testing of a blead perl with smartmatch removed/deprecated
could pick that up pretty quickly. I mean I have under-used experimental cpan
modules that have some test failures, but if they suddenly started throwing do
not compile errors[1], even I would pick them up.
[1] Not
On 14 Jun 2013, at 10:26, Kieren Diment dim...@gmail.com wrote:
[1] Not that I use many of the newer core features, occasionally I have to
account for some of my $work code having to work on 5.8.
I don't use smart match precisely because it doesn't feel intuitive and I have
enough to worry
On Fri, Jun 14, 2013 at 09:32:00AM +0100, jason wrote:
On 2013-06-14 09:11, Smylers wrote:
There isn't such a list -- its experimental nature means anything
might change. P5P doesn't have consensus, and no decision has been
made
on what's going to happen.
There are some on P5P suggesting
On Fri, 2013-06-14 at 19:26 +1000, Kieren Diment wrote:
Presumably CPAN testing of a blead perl with smartmatch removed/deprecated
could pick that up pretty quickly.
Automated CPAN testing occurs on new releases of modules only doesn't it
or is there comprehensive testing of every current
On Fri, Jun 14, 2013 at 02:13:00PM +0100, Jason Clifford wrote:
On Fri, 2013-06-14 at 19:26 +1000, Kieren Diment wrote:
Presumably CPAN testing of a blead perl with smartmatch removed/deprecated
could pick that up pretty quickly.
Automated CPAN testing occurs on new releases of modules
On Fri, Jun 14, 2013 at 02:13:00PM +0100, Jason Clifford wrote:
On Fri, 2013-06-14 at 19:26 +1000, Kieren Diment wrote:
Presumably CPAN testing of a blead perl with smartmatch removed/deprecated
could pick that up pretty quickly.
Automated CPAN testing occurs on new releases of modules only
On Fri, Jun 14, 2013 at 07:26:39PM +1000, Kieren Diment wrote:
Presumably CPAN testing of a blead perl with smartmatch removed/deprecated
could pick that up pretty quickly. I mean I have under-used experimental
cpan modules that have some test failures, but if they suddenly started
On Friday, 14 June 2013 at 07:51, David Cantrell wrote:
IIRC Zefram worked some dark magic to let you define custom
operators using XS.
Interesting. Quick, someone write a module that lets you hook this in Perl
space and then let the experimentation begin. After all, it doesn't have to be
On Friday 14 Jun 2013 16:29:23 Abigail wrote:
(If you hire more than a handful of new devs each month,
someone will not have gotten the memo).
Some people will think they /have/ got the memo because the feature's been
written about in the Camel book, Modern Perl, and no doubt other books too.
Putting my hand up as one of the idiots...
I've been using given/when for ages. My impression was that it was
announced as a new feature, yay perl has a case statement (only better)
at last, and I piled in. Maybe I passed danger signals on the way, but
not consciously. Lots of
13 matches
Mail list logo
