Márton Polgár

@chikega hi, just out of curiosity: what editor is this? How did you arrive here? I'm not sure how much can be done about something as ad-hoc as multi-line comments...

What really surprises me personally is that `&&` seems to be the same as `&`, or, analogously, `$$$$$foo` seems to be the same as `$foo`... I wonder why that is,...

I meant that `[ && ]` parses as a one-element array containing an anonymous callable variable `&`, converted to... a callable? Also, it would be good to see the use...

I think this is the same situation as ```raku my @x = (, ); .say for @x[0]; # (0 1) ``` and it would really cause further trouble if they...

On the other hand, there is `[Z]` which would do the right thing here, as @falsifian rightfully pointed out on the IRC. The reason is that the generated call is...

Some notes about the issue: - this never worked in bisectable times - `@.items` is a List (for some reason) while `@!items` is array[int] - probably related to the previous...

Note to self (and whoever else might be interested): `generate_accessor` in World.nqp might be worth checking...

I found the following behavior in pre-RakuAST world: - the parser recognizes the dot twigil [around here](https://github.com/rakudo/rakudo/blob/704a05b934ba10f3240e8764827bbfd7fe089cdf/src/Perl6/Actions.nqp#L3109) - rather than accessing the variable (not sure why?), it generates a method...

I think `is rw` does nothing here - as usual for @-sigilled variables, mind you. The mutability comes solely from the array. The gotcha is that this native array, when...

Two examples for the two fundamental platform types is okay, I think even a big fat disclaimer about process calls being heavily platform-dependent would do. Honestly, picking up the burden...