Hacker News Reader

My confusion was why the compiler didn't catch this, it is suppose to spot this sort of thing right?

Now that I think about it, maybe it has to do with `unsafe` block so the compiler doesn't check it.

My next question would be why does it need `unsafe`?

Ah yes, it's because of the `unsafe`.

> why does it need `unsafe`?

slice::from_raw_parts_mut is an unsafe function because it lets you conjure a slice from thin air; there's no checking of it at all.

This function is used because it's the most straightforward way of accomplishing the task.