[perl #130532] [JVM] Failing tests for itemization of arguments with infix: after introduction of Rakudo::Internals.OneValueIterator

2017-01-08 Thread via RT
# New Ticket Created by Christian Bartolomaeus # Please include the string: [perl #130532] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130532 > Since the new Rakudo::Internals.OneValueIterator is used in infix: (Rakudo

Re: A stricter typed variable

2017-01-08 Thread Salve J Nilsen
Hi, Fernando Santagata said: I my case, what I was trying to do is getting some strings in order to pass them over to a C function via NativeCall. Being sure the passed value was actually a string is not a whim, but would be useful in avoiding a segmentation fault. Yet I figure that as long

Re: [perl #130529] [Regression] After giving Seq it's own join method, redo behaves strange in grep

2017-01-08 Thread Elizabeth Mattijsen
Fixed with 362f674 , tests needed. > On 8 Jan 2017, at 14:11, Christian Bartolomaeus (via RT) > wrote: > > # New Ticket Created by Christian Bartolomaeus > # Please include the string: [perl #130529] > # in the subject line of all future correspondence about

[perl #130529] [Regression] After giving Seq it's own join method, redo behaves strange in grep

2017-01-08 Thread Christian Bartolomaeus via RT
On Sun, 08 Jan 2017 05:11:03 -0800, barto...@gmx.de wrote: > With rakudo commit 3c52aa096c Seq got it's own join method. For some > reason that changed the behaviour of 'redo' in 'grep' Also, next/redo in grep die on rakudo-j when using the new join method: $ ./perl6-j -e 'say (1..4).grep({next

[perl #130529] [Regression] After giving Seq it's own join method, redo behaves strange in grep

2017-01-08 Thread via RT
# New Ticket Created by Christian Bartolomaeus # Please include the string: [perl #130529] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130529 > With rakudo commit 3c52aa096c Seq got it's own join method. For some reason

Re: A stricter typed variable

2017-01-08 Thread Siavash
Note that you can also use subset to create a type: subset ArrayOfStr of Array where .all ~~ Str; sub foo (@a where ArrayOfStr) {...} or: sub foo (ArrayOfStr $a) {...} On 2017-01-08 10:33:36 GMT, Fernando Santagata wrote: > Thank you! > > On Sat, Jan 7, 2017 at 5:23 PM, Siavash

Re: A stricter typed variable

2017-01-08 Thread Fernando Santagata
Thank you! On Sat, Jan 7, 2017 at 5:23 PM, Siavash wrote: > > Hi, > > If you really want to avoid `Array[Str].new`, you can do something like > this: > > sub foo (@a where .all ~~ Str) {...} > > On 2017-01-07 11:45:55 GMT, Fernando Santagata wrote: > > Hello, > >