Jonathan Worthington

The significant difference is that: ``` my ($x,$y)=22,33; # OK ``` Is an assignment operation. The semantics are: 1. Declare `$x` and `$y` as if we'd written `my $x; my...

Yes; I suspect it will be rather easier to do in the RakuAST-based compiler, however, since I'm already planning to have standard destructures compiled there (rather than interpreted by the...

About this: ``` my NC-Library-Handle $LIBFOO = register-native-library('Foo', 'foo', :version(v42), :ENV); sub foo is native($LIBFOO); ``` That'd need to be `my constant ...`, because trait applications happen at compile time....

> Only the type is needed at compile time so the trait is created correctly, resolution happens at runtime, actually, I don't think so; the variable that exists at runtime...

@lizmat Is this issue resolved through the merge of #281?

> Preventing the pumpkin (or technical lead) to burn out is something very important, not only for the project but also for the human being behind the role. I can...

> Whatever is not in roast is not really specified. That leaves a big chunk of Rakudo functionality that does not have specification, sometimes is not tested, in some cases...

@niner Thanks, glad that it seems in the realm of feasibility. :-) Any thoughts on how that relationship between resource files and precomp files could be established?

Initial proposal: I see two main options. We could make it a compile-time error, so folks can't run into it accidentally. This avoids any further gotchas in this area. However,...

> ... The coercion is incorrect and should generate a run-time exception. This is what I'd expect, yes. > In other words, the coerced value would be temporarily stored, and...