> you need the call to free So how does ATS enforce memory safety? With Rust you have a bunch of library types that you can reuse that abstract away from the m

> you need the call to free So how does ATS enforce memory safety? With Rust you have a bunch of library types that you can reuse that abstract away from the memory management for you. The types make sure you don't screw up. Unfortunately you can't prove things about the `unsafe` blocks, and have to rely on careful auditing, but that only needs to be done once, and then you have a nice, reusable abstraction. Bookkeeping sucks. > What I really want is the next generation of dependently typed system languages which has learnt from the current ones. Agreed. At the moment Rust suits me the best, but I definitely don't think it is the end of the road.