The way we created/thrown new exceptions is very ad-hoc and needs more thought. Don't spec particular exceptions in new tests until we have the time to properly evaluate Exceptions hierarchy. http://colabti.org/irclogger/irclogger_log/perl6-dev?date=2018-09-21#l142
Remove all the files that are currently skipped. (e.g. S24-testing/1-basic.t, which probably needs to be fixed, as its tests are wrong and I don't see any other tests testing these routines)
Ensure Roast stresstest passes on Windows. Roast Issue #320 showing a bunch of failing tests.
Work in progress available in d-docs/New-Features-Policy.md
Collect all the features that will be new in 6.d. Many are already implemented,
documented, and are in use, but they're not part of 6.c language
(e.g. Str.parse-base)
Note, some routines are meant to be deprecated in 6.d but
we lack the means to emit a deprecation
warning based on language version.
These routines should be logged in release docs as deprecated even though they
might stick around for awhile and start to warn only in 6.e. These are listed
as planned for deprecation in deferred-to-6.e files.