On 11/19/24 08:36, Will Coleda wrote:
You should attach the code to the ticket - otherwise when theĀ snippet
times out, there's no record of the code. If it's in a git repo
somewhere, that's also fine, include a link to the specific code. In
general, the more golfed (shorter) the code is that sh
You should attach the code to the ticket - otherwise when the snippet times
out, there's no record of the code. If it's in a git repo somewhere, that's
also fine, include a link to the specific code. In general, the more golfed
(shorter) the code is that shows the issue, the better.
Regarding the
Hi All,
I am about to report a regression bug over on
https://github.com/rakudo/rakudo/issues/new
A question about bug reporting etiquette:
1) to reproduce the bug is 150 line of code. Do
I attach the code to the bug or do I post it
up on vpaste.net?
2) I have two different revision of Ra