niner

@vrurg there's actually one thing missing from the current spec test suite and the way we use it: Let's assume there is a test that tests that in Raku `1...

> > This can only be sound if it's postulated that all language versions MUST > > include all the previous versions, with a hard stop > Let's keep it...

I don't really like making changes to rakudo just to avoid making changes for this single user. Instead of that environment variable, you could also have the the Makefile copy...

In fact I don't :) Can't think of any

So far, the discussion has mostly been around "do we even need some design process". That's a bit of an academic question, as there is no suggestion of what such...

An alternative reading is, that the spec really does require a round-robin processing by Supply.zip and the current implementation of this method is just very fragile and relies on current...

@vrurg your proposal will always bring the problem that we'd need to act retroactively. Now we know that IO::Path would have needed to be version specific from the start. We...

> > That 6.c code calls .child and that method behaves...exactly like the 6.c code expected and how it was documented for 6.c at the time that 6.c code was...

> I miss your point here and how is signature is involved? If you want to know whether a multi method call will behave differently depending on language version, all...

I think the problems you listed for CURI can be solved within the implementation of CURI without requiring a full replacement. It's just that no one has given it a...