Re: changing name of module

2020-06-07 Thread Peter Pentchev
On Sun, Jun 07, 2020 at 02:28:08PM +0100, Richard Hainsworth wrote: > On 07/06/2020 13:31, Parrot Raiser wrote: > > Create an updated version, perhaps with an "rk" prefix, (preserving > > any text alignment, since "p6" and "rk" are the same length), then > > change the "pk" version simply to invoke

Re: changing name of module

2020-06-07 Thread Richard Hainsworth
Why nanoseconds slower? (I won't notice them, but why would a name change slow things?) If alignment is not a concern, then p6 and raku are equivalent? On 07/06/2020 13:31, Parrot Raiser wrote: Create an updated version, perhaps with an "rk" prefix, (preserving any text alignment, since "p6" a

Re: changing name of module

2020-06-07 Thread Parrot Raiser
Create an updated version, perhaps with an "rk" prefix, (preserving any text alignment, since "p6" and "rk" are the same length), then change the "pk" version simply to invoke the "rk"? Existing code should continue to work, albeit nanoseconds slower, while new code can be culturally consistent.

changing name of module

2020-06-07 Thread Richard Hainsworth
Hi, I've written some modules and released them into the Ecosystem. (I don't use cpan for raku) In the past, I have named my modules 'p6-xxx'. So references for zef would be git - finanalyst - p6-xxx (loosely speaking). Now I am considering whether to rename the module to `raku-xxx` There