[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

On 2018-02-16 09:01:57, c...@zoffix.com wrote: > On Fri, 16 Feb 2018 05:52:09 -0800, elizabeth wrote: > > I propose we change all onlies in the core to multis after the release > > and see how this breaks things / makes things slower. > > +1. Let's try. Yeah, sounds good. +1

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

On Fri, 16 Feb 2018 05:52:09 -0800, elizabeth wrote: > I propose we change all onlies in the core to multis after the release > and see how this breaks things / makes things slower. +1. Let's try.

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

On Fri, 16 Feb 2018 05:52:09 -0800, elizabeth wrote: > I propose we change all onlies in the core to multis after the release > and see how this breaks things / makes things slower. +1. Let's try.

Re: [perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

I propose we change all onlies in the core to multis after the release and see how this breaks things / makes things slower. > On 16 Feb 2018, at 14:17, Zoffix Znet via RT > wrote: > > Spotted another case where there's impact: whether or not a routine is a >

Re: [perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

I propose we change all onlies in the core to multis after the release and see how this breaks things / makes things slower. > On 16 Feb 2018, at 14:17, Zoffix Znet via RT > wrote: > > Spotted another case where there's impact: whether or not a routine is a >

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

Spotted another case where there's impact: whether or not a routine is a multi can have large impact on user's code. For example here: https://stackoverflow.com/questions/48819031/where-did-my-perl-6-operator-go-after-i-defined-a-more-specific-multi/48827522 As part of conventions, we'd need to

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

Spotted another case where there's impact: whether or not a routine is a multi can have large impact on user's code. For example here: https://stackoverflow.com/questions/48819031/where-did-my-perl-6-operator-go-after-i-defined-a-more-specific-multi/48827522 As part of conventions, we'd need to

Re: [perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

> On 18 Sep 2017, at 04:39, Brian S. Julin via RT > wrote: > > On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote: >> More comments on similar issue: https://irclog.perlgeek.de/perl6/2017- >> 09-17#i_15176823 >> >> Basically, a lot of core constructs

Re: [perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

> On 18 Sep 2017, at 04:39, Brian S. Julin via RT > wrote: > > On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote: >> More comments on similar issue: https://irclog.perlgeek.de/perl6/2017- >> 09-17#i_15176823 >> >> Basically, a lot of core constructs

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

On Sun, 17 Sep 2017 08:44:47 -0700, c...@zoffix.com wrote: > More comments on similar issue: https://irclog.perlgeek.de/perl6/2017- > 09-17#i_15176823 > > Basically, a lot of core constructs aren't workable with user-land > subclasses. Note on the performance concerns... if we had a

[perl #130020] [RFC][@LARRY] Create a set of conventions to minimize impact internal changes to user's code

Here's a link to the above IRC conversation, which continued after the quoted part: https://irclog.perlgeek.de/perl6/2016-11-04#i_13517260 To expand, it's not just Hashes that have this issue; Arrays, SetHash, and Complex also do, and probably many others. And the issue is not just about not