Re: list comprehension

2019-02-11 Thread Brad Gilbert
Actually I would suggest NOT adding Perl6, because the best way to create a Set is not to use “list comprehension”, but to just call `.Set` That whole page is about Set Builder Notation, but Perl6 doesn't actually have such a thing. You create a Set through a method call, or a subroutine call.

Re: subs and variables speed question

2019-02-11 Thread Timo Paulssen
> On 2/11/19 3:27 AM, Timo Paulssen wrote: > > WHICH doesn't give you a numerical value. just print it as it is. > > > $ p6 'sub a (Buf $b) { say $b.WHICH }; my $c = Buf.new(1,2,3); say > $c.WHICH; a($c);' > Buf|71848984 > Buf|71848984 > > If "moarvm has a moving garbage collector" moves my 100

Re: list comprehension

2019-02-11 Thread mimosinnet
Dear Brad, Thanks very much for the answer. I have been playing with your examples in the code below (and learned a lot!). Based on your insight, I would suggest these solutions to be added to the wikipedia: https://en.wikipedia.org/wiki/Set-builder_notation#Parallels_in_programming_languages

Re: subs and variables speed question

2019-02-11 Thread ToddAndMargo via perl6-users
On 11/02/2019 07:12, ToddAndMargo via perl6-users wrote: WHERE is pretty sweet command! $ p6 'sub a (Buf $b) { say $b.WHERE.base(0x10) }; my $c = Buf.new(1,2,3); say $c.WHERE.base(0x10); a($c);' 7F385D41334C 7F385D41334C On 11/02/2019 12:16, ToddAndMargo via perl6-users wrote: On 2/11/19

Re: subs and variables speed question

2019-02-11 Thread ToddAndMargo via perl6-users
On 2/11/19 2:52 AM, Timo Paulssen wrote: Please be aware that WHERE will give you the actual memory address of an object, but moarvm has a moving garbage collector, which means that objects can change their memory location. at the moment it will only happen up to two times, i believe. you'll

Re: subs and variables speed question

2019-02-11 Thread Timo Paulssen
Please be aware that WHERE will give you the actual memory address of an object, but moarvm has a moving garbage collector, which means that objects can change their memory location. at the moment it will only happen up to two times, i believe. you'll probably have a better result with .WHICH for