Don't let Alloy facts make your specs a fiction

·Hillel Wayne··

I’ve recently done a lot of work in Alloy and it’s got me thinking about a common specification pitfall. Everything in the main post applies to all formal specifications, everything in dropdowns is for experienced Alloy users. Consider a simple model of a dependency tree. We have a set of top-level dependencies for our program, which have their own dependencies, etc. We can model it this way in Alloy: sig Package { , depends_on: set Package } run {some depends_on} Show Alloy tip I’m going to use...

Read full article →

Related Articles

Computer Use is 45x more expensive than structured APIs
palashawas · Hacker News · 15d ago
Bun is being ported from Zig to Rust
SergeAx · Hacker News · 16d ago
Should I run plain Docker Compose in production in 2026?
pmig · Hacker News · 21d ago
Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem
ozkatz · Hacker News · 14d ago
RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust
atilimcetin · Hacker News · 16d ago