2 ms·
> but still a proof that what OP wrote is not valid in all cases. You are not proving anything until you post your Go code, which you don't seem to have done (
by caconym_ 10y ago
> but still a proof that what OP wrote is not valid in all cases.
You are not proving anything until you post your Go code, which you don't seem to have done (please correct me if I'm wrong, I am legitimately curious to see for myself how Go and Rust stack up against each other for this problem). Until then, all you're doing is making vague claims backed up by precisely zero evidence. Why should anyone take you seriously?
- lossolo 10y agoI have posted the code in reply to burntsushi. You can check it out yourself.