All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Isabelle's Design Philosophy: Why It Avoids Dependent Types and Proof Objects

By

baruchel

7mo ago· 9 min readenInsight

Summary

This article discusses the design philosophy behind the Isabelle proof assistant, explaining why it doesn't use dependent types or proof objects like other type theories. The author argues that proof objects are unnecessary and wasteful, and that Isabelle's approach of type checking in the implementation language (rather than in the logic) is more efficient. The piece explores the historical context of proof assistants, comparing different systems and their approaches to formal verification.

Key quotes

· 4 pulled
They are also completely unnecessary and a huge waste of space.
The two questions are essentially the same, because proof objects are intrinsic to all the usual type theories.
type checking in the implementation language (rather than in the logic) is more efficient
To be fair, nobody asks me this exact question. But people have regularly asked why Isabelle dispenses with proof objects.
Snippet from the RSS feed
02 Nov 2025

You might also wanna read