Darren Duncan

I agree that the 6.x versioning scheme is quite awkward and we should get away from that. My preference is to actually go back to version 1.0 instead of 6.e....

Well Apple was certainly treating Swift 1 as the next version of what used to be called Objective C, a total substitution. Does anyone know otherwise, that newer versions of...

> More than skipping, I'm worried about the syntax we're using. Because `use v7;` might be Perl's statement too. We need something more explicit, like `use raku;`, `use raku:ver;`, etc....

lizmat said: > I think the use of the word `use` for language versioning is a Perl-ism that we should deprecate. I would therefore propose a new statement, `language`, followed...

While we can use dates as a basis for version numbers, they should still be fully qualified with simple comparison rules and have longevity and account for any likely scenario....

> Use of full year would be a good option but apparently it will result in confusion with Rakudo versioning. It shouldn't cause confusion though. Using full years for versions...

Having my own experience with trademarks in this area (I trademarked "Muldis"), I believe its perfectly reasonable to trademark "Raku", but it may be good to broaden it a bit...

I have a proposal which may elegantly solve this problem. Raku should provide a more generalized literal syntax for arrays etc which uses literal index/value pairs, something like `[0:29,1:56,2:-3,100:42]` (illustrative,...

Following my prior comment for clarity: 1. What Muldis Object Notation has is not sparse arrays but rather dense arrays whose literals have an optional run-length encoding shorthand. So for...

An alternative proposal which on one hand seems possibly less elegant but may be a lot easier to implement, is that when one wants to represent a sparse array, they...