diff options
| author | colin <colin@cicadas.surf> | 2023-11-30 08:15:36 -0800 |
|---|---|---|
| committer | colin <colin@cicadas.surf> | 2023-11-30 08:15:36 -0800 |
| commit | a7f9f52a100b8ba8ef87b93ce6e227f9238e2902 (patch) | |
| tree | bd908174c308349904f3a6b4d8709a4b1a05200e /README.org | |
| parent | e75bc51f983d37ce9014957835615813b9e26e7c (diff) | |
typo; wording
Diffstat (limited to 'README.org')
| -rw-r--r-- | README.org | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -2,9 +2,9 @@ Terrafirma is a small system for defining data type validators that produce nice error messages on invalid data. -Terrafirma's main export is the =DEFVALIDATOR= macro. This macro defines a validator function. The body of the validator function evalutes in a special context. Within this context, the symbol =VALIDATE= is a macro that can be used to check predicates and singal a =VALIDATION-ERROR= upon failure: baslically just a wrapper around =ASSERT=. +Terrafirma's main export is the =DEFVALIDATOR= macro. This macro defines a validator function. The body of the validator function evalutes in a special context. Within this context, the symbol =VALIDATE= is a macro that can be used to check predicates and singal a =VALIDATION-ERROR= upon failure: basically just a wrapper around =ASSERT=. -The real "magic" happens when validation functions are defined in terms of other validation functions. In that case, error messages are nested to produce high-specific locations for your validation error. +The real "magic" happens when validation functions are defined in terms of other validation functions. In that case, validation errors are nested to produce highly-specific messages for your validation error. Here is an example: |