Tag
C++26 introduces a new <debugging> header with std::breakpoint(), std::is_debugger_present(), and std::breakpoint_if_debugging(), standardized via papers P2546R5 and P2810R4 to replace platform-specific debugging macros.
A fan-written deep dive into Gleam's case exhaustiveness checking, exploring compiler-core/src/exhaustiveness.rs and tracing the pattern-matching compilation theory back to Lennart Augustsson's 1984 "Compiling Pattern Matching" paper.
An introductory tutorial on the C++26 contracts feature (P2900), showing how preconditions and postconditions replace traditional assert-based checks, along with compiler options, evaluation semantics, and common pitfalls.
一条推文引用了 Elon Musk 关于未来的观点：软件将不再以人类可读的代码形式存在，AI 模型可以直接生成机器码，人类只需描述需求并验证结果。
Martin Odersky, creator of Scala, argues that types will become the contract between humans and AI-generated code, helping humans maintain control as AI writes and exploits vulnerabilities in code at scale.
Rust 语言设计师 Niko Matsakis 撰文探讨 LLM 智能体（agentic development）对编程与编程语言设计的影响，认为 Rust 的类型系统和可靠性使它非常适合智能体驱动的开发，并展望如何进一步强化这一优势。
标题指出在 Rust 借用检查器中发现了存在 11 年之久的 unsoundness 缺陷，内容实际为 Rust 主仓库的 README。该发现对 Rust 的内存安全保证具有重要意义。
Valen 的新文章介绍了一种更灵活的借用检查器（group borrowing），编译器会记住引用指向的位置，以实现比 Rust 更简单灵活的内存安全方案，并已被 Google Carbon 等语言采纳。
A blog post by a Rust programmer detailing quirky C language behaviors learned while self-teaching C, including booleans via <stdbool.h>, null-terminated strings versus Rust's length-prefixed &str, and related memory trade-offs. It serves as a practical companion guide for developers transitioning from Rust to C.
Alan Kay's 1993 HOPL-II paper recounts the early history of Smalltalk at Xerox PARC, tracing its roots in 1960s human-computer symbiosis research, the FLEX machine, SketchPad/Simula, and the Dynabook vision toward object-oriented design.
An opinion piece arguing that Common Lisp is now the best programming language because LLMs shift the bottleneck from writing code to fast feedback loops, live image-based development, interactive debuggers, and macro-driven domain-specific languages that cut code volume and token costs.
Ron Pressler of Oracle's Java platform group explains the theoretical motivation for Project Loom, which aims to add continuations and fibers to the JDK to simplify nondeterministic I/O and concurrency in Java.
DHH had AI agents rewrite Basecamp's Campfire chat app in Elixir, Go, and Rust, showing nearly 150x performance gaps versus Ruby, and argued that AI agents writing code may shift language choice from developer ergonomics to runtime efficiency.
A discussion post arguing that if LLMs write most code, we should design a single AI-oriented language where users describe intent and constraints while the compiler decides implementation details across languages like Go, Java, or SQL.
1989 paper on the Self language compiler introducing procedure customization by receiver type, speculative type predictions with runtime tests, call splitting, and aggressive inlining — techniques that doubled the performance of dynamically-typed OO languages and later informed modern JITs.
A conference talk recap: an engineer recounts the journey of breaking up with Node, falling in love with Rust, and using it to found Oxide Computer Company, along with porting Rust support to illumos — and how Rust's rigor and performance values became the cornerstone of the company culture.
A discussion arguing that Rust may fade as the default language for AI coding agents due to long compile times and agents becoming adept at manual memory management in other languages.
A blog post arguing that despite an 'existential crisis' mood among programming-languages researchers fearing AI will make humans stop writing code, the field is entering an era of unprecedented exploration where LLMs accelerate research and the beautiful theoretical ideas of PL remain as compelling as ever.
Interview with Peter Bex, a CHICKEN Scheme maintainer and professional Clojure developer, covering his path from C64 BASIC to Lisp, his core contributions to CHICKEN Scheme (numerical tower, irregex, security fixes), and reflections on Scheme's community, Racket, Postgres, and Clojure.
The Futhark team explains why their compiler's GPU pipelines force all arrays into GPU memory, making sequential CPU-side work (like greedy distance-2 graph colouring for sparse Jacobians) three orders of magnitude slower, and describes a hack that allows keeping some functions off the GPU while still exploiting GPU parallelism for the rest of the program.