News for hackers. Stuff that matters.

A comment on Why Rust closures are somewhat hard. Parent comment

Re:Why Rust closures are somewhat hard by geezerjay on Tuesday September 11, 2018 @01:24AM (#17957368)
It isn't. The hypothetical problem was setting a pointer to a stack variable. That's a no-no from the start, and adding hypothetical closures to the mix changes nothing.
[ Parent | on HN ]
Re:Why Rust closures are somewhat hard by samnardoni on Tuesday September 11, 2018 @02:46AM (#17957632)
Having a pointer to a stack variable is fine, as long as the stack variable lives longer than the closure.
[ Parent | on HN ]
Re:Why Rust closures are somewhat hard by naasking on Tuesday September 11, 2018 @08:21AM (#17959018)
Right, so your original claim about properly cleaning up is not the only problem with closures in C. There are quite a few hazards actually.
[ Parent | on HN ]
Re:Why Rust closures are somewhat hard by geezerjay on Tuesday September 11, 2018 @11:24AM (#17960558)
> Right, so your original claim about properly cleaning up is not the only problem with closures in C.

Your comment makes no sense. OP stated that your hypothetical problem isn't even a problem if the developer knows what he is doing, and your take from that is that there are more problems?

[ Parent | on HN ]
Re:Why Rust closures are somewhat hard by naasking on Tuesday September 11, 2018 @12:58PM (#17961419)
The original poster said the trouble was cleaning up after the closure is no longer needed. That's clearly not the case as this thread has covered. I thought the previous poster was the original poster, so just replace "your original claim" with "the original claim".
[ Parent | on HN ]