<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ltl on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/ltl/</link>
    <description>Recent content in Ltl on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Apr 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/ltl/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Why Specifications Don&#39;t Compose</title>
      <link>https://www.hillelwayne.com/post/spec-composition/</link>
      <pubDate>Sun, 18 Apr 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/spec-composition/</guid>
      <description>Recently my friend Lars Hupel and I had a discussion on why formal methods don&amp;rsquo;t compose well. You can read the conversation here. We focused mostly on composing formally-verified code. I want to talk a little more about the difficulties in composing specifications. This is half because it&amp;rsquo;s difficult for interesting reasons and half because it&amp;rsquo;s a common question from beginners.
Beginners to formal specification expect specifications should be organized like programs: multiple independent modules that interact through public interfaces, where the modules don&amp;rsquo;t know about each others&amp;rsquo; private implementations.</description>
    </item>
    
  </channel>
</rss>