News for hackers. Stuff that matters.

A comment on Getting Past C. Parent comment

Re:Getting Past C by wildmusings on Wednesday January 04, 2017 @01:30AM (#13316122)
His point is that you're not forced to do that. And anyhow, that doesn't solve the issue since you can bungle the creation of the slice with the wrong offset or length.
[ Parent | on HN ]
Re:Getting Past C by Manishearth on Wednesday January 04, 2017 @01:36AM (#13316147)
I wasn't refuting their point. I was just pointing this out.

However, you can't bungle the creation of a slice in rust without using explicitly marked unsafe code.

[ Parent | on HN ]
Re:Getting Past C by wildmusings on Wednesday January 04, 2017 @01:42AM (#13316171)
Not bungle in the sense of overflowing the underlying buffer, but overflowing the logical buffer that is contained within it, i.e. getting the wrong slice.
[ Parent | on HN ]
Re:Getting Past C by Manishearth on Wednesday January 04, 2017 @02:07AM (#13316263)
Oh, sure. Like I said, I wasn't refuting their point.
[ Parent | on HN ]