Unsigned sizes: a five year mistake

C3 is the ergonomic, safe evolution of C. Familiar syntax, full ABI compatibility, optionals, slices, contracts and zero-cost abstractions.

C3 Programming Language
All of the String types

A list of all of the string types in a lot of languages

A Case Against Currying - emih.com

An Incoherent Rust

Coherence and the orphan rules are a frequent source of complaints about Rust, and a common topic of language proposals. This post covers most of the existing proposals around coherence and my vision for how we should solve coherence once and for all.

No Semicolons Needed | Terts Diepraam

Slices combine a mutable vector with a (seemingly) read-only view – a big mistake in #Go, leading to the foot-guns here & in the discussions 😓:

“Sliced By Go’s Slices”, Ohad Ravid (https://ohadravid.github.io/posts/2026-02-go-sliced/).

Via Lobsters: https://lobste.rs/s/o3cpxf/sliced_by_go_s_slices

#Programming #GoLang #PLDI

Sliced by Go’s Slices

Today, I was sliced by Go’s slices. Actually, by Go’s variadics. Question: what does this snippet print? func main() { nums := []int{1, 2, 3} …

six thoughts on generating c — wingolog

wingolog: article: six thoughts on generating c

Another excellent post 👌🏽 from Russ Cox 👇🏽🫡:

“Floating-Point Printing And Parsing Can Be Simple And Fast” (https://research.swtch.com/fp).

On HN: https://news.ycombinator.com/item?id=46685317

On Lobsters: https://lobste.rs/s/nbsclr/floating_point_printing_parsing_can_be

#Programming #Math #FloatingPoint #Numbers #PLDI #Parsing #Printing

research!rsc: Floating-Point Printing and Parsing Can Be Simple And Fast (Floating Point Formatting, Part 3)

Eurydice: a Rust to C compiler (yes)

Perhaps the greatest surprise of the last two years was, for me, the realization that people not only care about compiling C to Rust (for obvious reasons, such as, ahem, memory safety) – they also care about compiling Rust to C! Wait, what?

Jonathan Protzenko
Generating C code that people actually want to use

Project Everest is a large, collaborative research effort that aims to verify and deploy a new, secure HTTPS stack. All of our code is verified using the F* programming language. Using KreMLin, a dedicated compiler, the verified F* code is compiled to readable C, meaning existing systems projects can readily integrate our verified code. Going to C is what allows people to use our code without having to buy into exotic, strange languages with lambdas.

Jonathan Protzenko