>>10,13
All bets are off when it comes to -e. The only virtue here is you can cram it all in. The formatting provided is terrible, but it has nothing on your average IOCCC loser. See
>>31.
>>14
You can use either. There's a good reason to use colons though:
@list.reduce: {
#comlex multiline recucer function
}
Seeing the likes of
({ ... }) in javascript is so bad and so common I had to change my font.
>>20
It's just bitwise negation, but with arguments explicitly coerced to Int first. It's not too hard to remember, since prefix
+ explicitly numifies objects and is generally used for numeric context.
>>29
I'm still playing with Rakudo Star, though
You'll be a lot better off in April. A new GC is coming with serious improvements. My tests show it's much faster for real programs and is much better at keeping memory usage low. A program I had which triggered a degenerate case in the old GC consuming ~3 gigs, now seems to level off at about 130MB.
There's also improvements to the object model which will apparently speed up just about everything by a great deal.
>>30
What exactly would you take out? The setting? If so: what do you think is stopping you? Still too much stuff in? Try nqp maybe?