cry/nixide
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc: Clarify why we test call and apply and how they relate

Browse source 
(cherry picked from commit 17c7a8d30d1c4d99eeb84a6203ae33d2ba781edb)
This commit is contained in:
Robert Hensing 2024-06-14 19:32:56 +02:00
parent b04d429f19
commit 93a2db836a
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
rust/nix-expr/src/eval_state.rs
View file

@ -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();