From 523ed86eabbfec43400c62445ed6b579995cf0c8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Sun, 29 Jul 2018 07:58:18 +0200 Subject: [PATCH] Update bsip-0040.md --- bsip-0040.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsip-0040.md b/bsip-0040.md index a9a27ac..9948025 100644 --- a/bsip-0040.md +++ b/bsip-0040.md @@ -83,7 +83,7 @@ List of possible asserts are: | `limit_monthly` | [`max_cumsum`, `interval_in_months`] | [`current_cumsum`, `interval_began`] | | `attribute_assert` | `attribute_to_assert` = [{`attribute_identifier`: `any of above assert_objects`}] | stateless | -There is no implicit type conversion when attempting to assert, incompatible type means assert failure. If required, a field can be added that stores the assumed type of the argument (if conversion fails, assert fails). +There is no implicit type conversion when attempting to assert, incompatible type means assert failure. If required, a field can be added that stores the assumed type of the argument (if conversion fails, assert fails). If an argument has no asset, it is unrestricted and may be given (or not for optional arguments) with any value. In the following we list possible `asserts`. Mentioning `argument value` refers to the value of the argument of the operation specified `argument` in `assert_object`. The logic does not differentiate if an `argument` is optional or mandatory. All asserts imply: If the `argument` is given, it must pass the `assert`. If the `argument` is not given, assert is implicitly passed.