programming languages

A practical guide through the landscape of type systems, from everyday generics to dependent types that prove correctness, with examples in Rust, Scala, and Idris

Concrete’s constraints have real costs. Linear cleanup is verbose, no closures hurt composition, and the ecosystem barely exists. Here is what the language actually makes harder.

I ran an autoresearch-style loop on a Concrete program. The compiler told an agent where authority, allocation, and proof surface could improve and confirmed when those properties changed. No profiler, no benchmark noise. Your compiler can answer questions instead of saying pass/fail.

Edgar Luque is right that AI creates a new barrier for programming languages. He is wrong that the barrier is universal. Languages designed for machine generation and machine verification invert the problem entirely.

Wuyts is right about effects and ownership. The Hacker News skeptics are right about complexity. Concrete accepts both and says no to refinement types.

Concrete is a systems language designed so the compiler can reason about what code does: authority, allocation, resource lifetimes, and proof surface.