From 371ddd5dc867122e0b3a647833efeb5f3f6f2f79 Mon Sep 17 00:00:00 2001 From: Valentin Gagarin Date: Wed, 14 Jun 2023 12:45:02 +0200 Subject: [PATCH] fix typo --- rfcs/0137-nix-language-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/0137-nix-language-version.md b/rfcs/0137-nix-language-version.md index d2c0ea0..cbd1865 100644 --- a/rfcs/0137-nix-language-version.md +++ b/rfcs/0137-nix-language-version.md @@ -317,7 +317,7 @@ Other discussions around language changes: - (+) This would be beneficial for alternative implementations in terms of churn and effort to keep up - Or implementors of alternative evaluators catching up with changes - (+) Specifying the language precisely via the version actually offers alternative implementations an alternative to catching up: only support a given language version - - (+) This essentially nudges one to organise Nix language (specification or evaluator implementation ) development to be more independent of the rest of Nix + - (+) This essentially nudges one to organise Nix language (specification or evaluator implementation) development to be more independent of the rest of Nix This is good, since it in turn forces stronger separation of concerns and more architectural clarity - (-) Prohibits best-effort attempts at evaluating expressions with possibly incompatible evaluators - (+) With the proposed level of strictness, one doesn't have to rely on best effort but can instead be explicit