From d1812dbcc483e40843a0d8ed1fd915654cba0f89 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Fri, 27 Aug 2021 09:54:07 +0300 Subject: blog: decision on scenario step implementation language Sponsored-by: author --- blog/2021/08/27/step-language.mdwn | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 blog/2021/08/27/step-language.mdwn diff --git a/blog/2021/08/27/step-language.mdwn b/blog/2021/08/27/step-language.mdwn new file mode 100644 index 0000000..9117d95 --- /dev/null +++ b/blog/2021/08/27/step-language.mdwn @@ -0,0 +1,23 @@ +[[!meta date="Fri, 27 Aug 2021 09:34:14 +0300"]] +[[!tag decision]] +[[!meta title="Decision: Use Rust for Subplot scenario step implementation"]] + +I will be using [Subplot][] to document the requirements and +acceptance criteria for `sshca`, and for automating the verification +that they are met. The approach in Subplot is to write semi-formal +_scenarios_ that get translated into code, using functions that +implement each scenario step. I can choose between the Python and Rust +languages for writing those scenarios. I choose Rust, because it +allows more concurrency when the verification code is running, and +also I find I can write correct code more easily in Rust than in +Python. + +The only reason to choose Python would be to make the step functions +be more easily audited by people other than me, but I think Rust has +already become sufficiently popular that Rust will not be a problem. +It's more important that the actual requirements, acceptance criteria, +and the scenarios are understood by anyone interested. + +The actual code for `sshca` will be written in Rust in any case. + +[Subplot]: https://subplot.liw.fi/ -- cgit v1.2.1