So I guess the first question I have is whether the 'auto-joining' of array
elements is specc'ed or not.
What you seem to be saying is that when calling a function on an array, the
first response is for Raku to call something similar to 'cat' on the array,
then proceed to process the function call
On 10/10/2020 23:21, William Michels via perl6-users wrote:
> So I guess the first question I have is whether the 'auto-joining' of
> array elements is specc'ed or not.
>
> What you seem to be saying is that when calling a function on an
> array, the first response is for Raku to call something sim
William Michels wrote:
>I actually wondered where the different programming paradigms
>would be delineated
I think were the present topic has to do more with the
strong/weak/gradual typing debates-- here Raku is doing an
automatic type conversion that a "strong-typing" fanatic
would sneer at. Th
Functions in Raku tend to have one job and one job only.
`split` splits a string.
So if you call `split` on something that is not a string it gets turned
into one if it can.
This happens for most functions.
Having `split` be the only function that auto-vectorizes against an array
would be very
On Sat, 10 Oct 2020, William Michels via perl6-users wrote:
> So I guess the first question I have is whether the 'auto-joining' of array
> elements is specc'ed or not.
>
I did not find anything that explicitly requires @array.split() to force
@array into a string, but there are tests in S02-type
On Sun, 11 Oct 2020, Tobias Boege wrote:
> On Sat, 10 Oct 2020, William Michels via perl6-users wrote:
> > then proceed to process the function call. As it is my understanding that
> > Raku incorporates a lot of different programming paradigms (imperative,
> > object-oriented, functional, etc.), I'
