Update test comment.

adpaco-aws · Jul 29, 2024 · 206a35c · 206a35c
1 parent ffd858c
commit 206a35c
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 11 deletions.
diff --git a/tests/expected/safety-constraint-attribute/abstract-value/abstract-value.rs b/tests/expected/safety-constraint-attribute/abstract-value/abstract-value.rs
@@ -1,9 +1,8 @@
 // Copyright Kani Contributors
 // SPDX-License-Identifier: Apache-2.0 OR MIT
 
-//! Check that the `#[safety_constraint(...)]` attribute automatically generates
-//! the `Arbitrary` implementation, and also that the values it generates
-//! respect the type invariant.
+//! Check that the `#[safety_constraint(...)]` attribute is picked up when
+//! deriving the `Arbitrary` and `Invariant` implementations.
 
 //! In this case, we test the attribute on a struct with a generic type `T`
 //! which requires the bound `From<i32>` because of the comparisons in the

diff --git a/tests/expected/safety-constraint-attribute/check-arbitrary/check-arbitrary.rs b/tests/expected/safety-constraint-attribute/check-arbitrary/check-arbitrary.rs
@@ -1,9 +1,8 @@
 // Copyright Kani Contributors
 // SPDX-License-Identifier: Apache-2.0 OR MIT
 
-//! Check that the `#[safety_constraint(...)]` attribute automatically generates
-//! the `Arbitrary` implementation, and also that the values it generates
-//! respect the type invariant.
+//! Check that the `#[safety_constraint(...)]` attribute works as expected when
+//! deriving `Arbitrary` and `Invariant` implementations.
 
 extern crate kani;
 use kani::Invariant;

diff --git a/tests/expected/safety-constraint-attribute/check-invariant/check-invariant.rs b/tests/expected/safety-constraint-attribute/check-invariant/check-invariant.rs
@@ -1,8 +1,8 @@
 // Copyright Kani Contributors
 // SPDX-License-Identifier: Apache-2.0 OR MIT
 
-//! Check that the `#[safety_constraint(...)]` attribute automatically generates
-//! the `Arbitrary` and `Invariant` implementations for the annotated type.
+//! Check that the `#[safety_constraint(...)]` attribute works as expected when
+//! deriving `Arbitrary` and `Invariant` implementations.
 
 extern crate kani;
 use kani::Invariant;

diff --git a/tests/expected/safety-constraint-attribute/grade-example/grade-example.rs b/tests/expected/safety-constraint-attribute/grade-example/grade-example.rs
@@ -1,9 +1,8 @@
 // Copyright Kani Contributors
 // SPDX-License-Identifier: Apache-2.0 OR MIT
 
-//! Check that the `#[safety_constraint(...)]` attribute automatically generates
-//! the `Arbitrary` implementation, and also that the values it generates
-//! respect the type invariant.
+//! Check that the `#[safety_constraint(...)]` attribute works as expected when
+//! deriving `Arbitrary` and `Invariant` implementations.
 
 //! In this case, we test the attribute on a struct that represents a hybrid
 //! grade (letter-numerical) which should keep the following equivalences: