Because Rakudo development has shifted from master to ng for the moment, while some significant changes are being made to the spec, we are setting master to point to a fixed older release of the spectests. This means we can make changes to the spectests without creating "regressions" in Rakudo master.
…er than Rat.new. This means that Rat math will automatically fall back to Num math if the intermediate values cannot be represented as Ints in Rakudo. (Previously it would yield a cryptic error message because Rat.new insisted on Int arguments.)
This wins us back most spectests. Most remaining failures are related to autovivification returning Failure, not Mu.
Actually, these pass the spectest but the Rat.sign one is definitely returning the wrong thing. Will try to correct both spectest and code shortly.
...from the 'git log'.
…ted siggies thing really is.
… 5 fail Failure summary: S02-lexical-conventions/unicode.rakudo aborted 5 test(s) S06-signature/named-parameters.rakudo passed 81 unplanned test(s)
…than taking +self.
s/or/and/; The code has a && in the corresponding place, which makes much more sense.
This has a spectest failure, t/spec/S12-attributes/instance.t, but that already existed at the previous PARROT_REVISION as well. This Parrot is reputed to have solved a major memory leak.
This resulted in split() also returning Strings. jnthn++ for suggesting the correct fix.
… 15 fail Failure summary: S02-lexical-conventions/unicode.rakudo aborted 5 test(s) S12-introspection/methods.t aborted 10 test(s)