Vadim Belman
Vadim Belman
This bug affects only the legacy compiler. The code works with RakuAST. Unless somebody knows how to fix it in under 5 minutes, currently makes no sense of wasting time...
The refactoring is in the process. I don't currently have much time to explain, try googling for RakuAST. If this doesn't work for you then either me or somebody else...
BTW, thank you for reminding me as I wanted to add the label to this issue.
> Or alternatively it could be an option in `ListenerOptions` to attempt to delete any existing file rather than returning `AddrInUse`? This is a very bad idea. Consider accidentally started...
I'm not really sure. Besides, I suspect that there was another factor which, as I suspect, may have contributed to the situation: it is likely that the default toolchain was...
To me the explanation in the original version of the doc is good enough to support deprecation. I just wonder how much is it used in the ecosystem?
Looks like a funny side-effect of `unit` work merge. The real error, and this is what is reported on 2021.12, is failing typecheck against `$sorted-keys`, which remains uninitialized but the...
> Anyways, it seems to affect things that are pre-compiled: This code produces the correct error message: > > ```raku > sub a(Bool :$a) { }; sub b(:$a) { a...
Can we deprecate both? Because otherwise, speaking of consistency, we'd need `si`, `mi`, etc.
I don't think the `BEGIN` case has something to do about the original issue. It looks more like something went wrong with serialization. Yet, the original bug winds down to...