Hacker News new | past | comments | ask | show | jobs | submit | from login
Exploring Seamless Rust Interop for Newer Languages, Part 1 (verdagon.dev)
1 point by PaulHoule 9 days ago | past | discuss
Exploring Seamless Rust Interop for Newer Languages (verdagon.dev)
2 points by ingve 14 days ago | past
Exploring Seamless Rust Interop for Newer Languages, Part 1 (verdagon.dev)
8 points by todsacerdoti 17 days ago | past | 2 comments
Layer-wise inferencing and batching: Small VRAM doesn't limit LLM throughput (verdagon.dev)
2 points by verdagon 25 days ago | past
Layer-wise inferencing and batching: Small VRAM doesn't limit LLM throughput (verdagon.dev)
5 points by one-punch 26 days ago | past
Higher RAII and the seven arcane uses of linear types (verdagon.dev)
99 points by agluszak 26 days ago | past | 46 comments
Higher RAII, and the Seven Arcane Uses of Linear Types (verdagon.dev)
10 points by ingve 27 days ago | past | 1 comment
Borrow Checking, RC, GC, and the Eleven () Other Memory Safety Approaches (verdagon.dev)
189 points by todsacerdoti 46 days ago | past | 68 comments
Chasing the Myth of Zero-Overhead Memory Safety (verdagon.dev)
1 point by cyber_kinetist 8 months ago | past
Vale's first prototype for immutable region borrowing (verdagon.dev)
395 points by modernerd 11 months ago | past | 139 comments
Making C++ safe without borrow checking, reference counting, or tracing GC (verdagon.dev)
275 points by jandeboevrie 11 months ago | past | 214 comments
Chasing the Myth of Zero-Overhead Memory Safety (verdagon.dev)
4 points by obl 11 months ago | past | 1 comment
Memory safety without borrow checking, reference counting, or garbage collection (verdagon.dev)
111 points by modernerd 12 months ago | past | 93 comments
Single Ownership and Memory Safety Without Borrow Checking, RC, or GC (verdagon.dev)
3 points by verdagon 12 months ago | past | 1 comment
What Vale Taught Me About Linear Types, Borrowing, and Memory Safety (verdagon.dev)
4 points by pjmlp on June 2, 2023 | past
What Vale taught me about linear types, borrowing, and memory safety (verdagon.dev)
126 points by generichuman on June 1, 2023 | past | 12 comments
Implementing Vale's Region Borrowing, and Its Unexpected Quest (verdagon.dev)
2 points by Miaourt on May 9, 2023 | past
How to Survive Your Project's First 100k Lines (verdagon.dev)
214 points by swah on May 3, 2023 | past | 81 comments
How Memory safety approaches speed up and slow down development velocity (verdagon.dev)
141 points by signa11 on Jan 17, 2023 | past | 137 comments
Memory Safety Approaches Speed Up and Slow Down Development Velocity (verdagon.dev)
2 points by diegocg on Jan 16, 2023 | past
Implementing a New Memory Safety Approach, Part 1 (verdagon.dev)
5 points by verdagon on Nov 22, 2022 | past
Zero-Cost Memory Safety with Vale Regions (Preview) (verdagon.dev)
4 points by karterk on Nov 18, 2022 | past
Hash Codes, Non-Determinism, and Other Eldritch Horrors (verdagon.dev)
31 points by GarethX on Nov 10, 2022 | past | 5 comments
Hash Codes, Non-Determinism, and Other Eldritch Horrors (verdagon.dev)
3 points by verdagon on Nov 9, 2022 | past
When to use memory safe languages (verdagon.dev)
27 points by azhenley on Oct 8, 2022 | past | 57 comments
Vale's Hybrid-Generational Memory (verdagon.dev)
1 point by todsacerdoti on July 28, 2022 | past
Heisenbugs: The most elusive bug. How to capture them with Perfect Replayability (verdagon.dev)
2 points by PainfullyNormal on June 29, 2022 | past
Next-Gen Language Features: User Code on the GPU (verdagon.dev)
2 points by verdagon on June 27, 2022 | past
Fearless FFI: Memory Safety, Safer Dependencies, Supply-Chain Attack Mitigation (verdagon.dev)
7 points by izackp on June 23, 2022 | past
Vale's “Fearless FFI”, for Memory Safety, Safer Dependencies, and Supply-Chain (verdagon.dev)
5 points by todsacerdoti on June 22, 2022 | past

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: