From 93a2db836a140cf18750ed20766580d7774acc0e Mon Sep 17 00:00:00 2001
From: Robert Hensing <robert@roberthensing.nl>
Date: Fri, 14 Jun 2024 19:32:56 +0200
Subject: [PATCH] doc: Clarify why we test call and apply and how they relate

(cherry picked from commit 17c7a8d30d1c4d99eeb84a6203ae33d2ba781edb)
---
 rust/nix-expr/src/eval_state.rs | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/rust/nix-expr/src/eval_state.rs b/rust/nix-expr/src/eval_state.rs
index 592abb1..1e21e19 100644
--- a/rust/nix-expr/src/eval_state.rs
+++ b/rust/nix-expr/src/eval_state.rs
@@ -1050,6 +1050,7 @@ mod tests {
         .unwrap();
     }
 
+    /// This tests the behavior of `call`, which is strict, unlike `new_value_apply`.
     #[test]
     fn eval_state_call_fail_args() {
         gc_registering_current_thread(|| {
@@ -1071,8 +1072,9 @@ mod tests {
         .unwrap();
     }
 
+    /// This tests the behavior of `new_value_apply`, which is lazy, unlike `call`.
     #[test]
-    fn eval_state_apply_fail_args() {
+    fn eval_state_apply_fail_args_lazy() {
         gc_registering_current_thread(|| {
             let store = Store::open("auto", HashMap::new()).unwrap();
             let es = EvalState::new(store, []).unwrap();