Jonathan Worthington

Indeed, NativeCall isn't actually part of the language spec. This can happen as soon as somebody has the time/patience to make it happen. For @Xliff or anyone who wants to...

We could allow `(...)` and `[...]` with the same semantics as we have for parameter checking - that is to say, they'd parse a signature inside of them, the latter...

> Multiple-returns in the R-programming language is accomplished by placing the return items into a singular data object, usually a list. In doing so the items obtain a positional value,...

> It also sounds like we have at least a plan for an implementation – coerce the returned value to a Capture and match on it. Yes, that's probably the...

Yes, the intro text really should be more focused on Perl 6 the language, not Perl 6 the project, at this point. For examples, I'd probably focus on ones that...

> We can't go back to 3, but I believe we can go to 7.0.0 or higher and drop the lettering I was about to write "we'd probably have to...

> No, we're not going to change the version backwards. Certainly anything that happens has to have the version literals compare correctly, so the version literal of whatever new number...

Also, with regard to the `language` keyword proposals, I'll ponder it some, but my initial feeling is that I'm not thrilled about another keyword. I think `use` is huffmanized about...

@autarch Thanks to you and TPF for looking in to this. I share the concerns expressed here on the language specification vs. language implementation difference, and think it's important the...

Sorry, somehow forgot to reply, but I'd be in favor of the two also.