Hacker News new | ask | show | jobs
by foxes 1172 days ago
That sounds like if you write proper C code correctly you don’t make memory errors when in reality it’s very common to not write correct code.

That’s why rust came along, to stop that behaviour, you simply can’t make that mistake, and hence the point is maybe there’s a better test to use than p value as a standard.

1 comments

How else do you propose to construct procedures that control type I error and evaluate their properties?