From 2bd776ec55c9e0382bb4dc492475e619ebeef1b4 Mon Sep 17 00:00:00 2001 From: Danila Fedorin Date: Sun, 14 May 2023 21:18:23 -0700 Subject: [PATCH] Add a description and disclaimer to the Alloy draft. --- content/blog/dyno_alloy/index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/blog/dyno_alloy/index.md b/content/blog/dyno_alloy/index.md index 04e0f46..2598944 100644 --- a/content/blog/dyno_alloy/index.md +++ b/content/blog/dyno_alloy/index.md @@ -2,9 +2,16 @@ title: "Proving My Compiler Code Incorrect With Alloy" date: 2023-05-02T22:48:52-07:00 tags: ["Compilers", "Alloy"] +description: "In this post, I apply Alloy to a piece of code in the Chapel compiler to find a bug." draft: true --- +__Disclaimer:__ though "my compiler code" makes for a fun title, I do not +claim exclusive credit for any of the C++ code in the Chapel compiler that +I mention in this post. The code is "mine" in the sense that I was +debugging changes I was making, and perhaps also in the sense that I was +working with it. + I work as a compiler developer on the [Chapel](https://chapel-lang.org) team. Recently, while thinking through a change to some code, I caught myself making wishes: "if only I could have a computer check this property for