Skip to content
The Nexus
DossierENTITY

memory safety

Coverage of memory safety in the Nexus archive.

Earliest in view: Apr 19 · 21:00 UTCMost recent: May 24 · 18:31 UTC
Co-mentioned in this coverage
Recent coverage
  • TECHNOLOGYMay 24 · 18:31 UTCHACKER NEWS
    Migrating from Go to Rust

    The article provides a migration guide for developers transitioning from Go to Rust, focusing on key differences in syntax, memory management, and performance considerations. It highlights Rust's safety features and zero-cost abstractions as advantages over Go.

  • TECHNOLOGYApr 29 · 02:19 UTCHACKER NEWS
    Bugs Rust Won't Catch

    The article 'Bugs Rust Won't Catch' discusses limitations in Rust's safety guarantees, highlighting scenarios where bugs may still occur despite the language's focus on memory safety. It references a blog post on corrode.dev and a Hacker News discussion thread.

  • TECHNOLOGYApr 19 · 21:00 UTCHACKER NEWS
    C++26: Reflection, Memory Safety, Contracts, and a New Async Model

    C++26 introduces key features including reflection, enhanced memory safety, formal contracts, and a new asynchronous programming model. These updates aim to modernize the language, improve developer productivity, and address long-standing challenges in systems programming.

memory safety · Dossier · The Nexus