|
|
@ -28,8 +28,7 @@ already be available.
|
|
|
|
<provides>
|
|
|
|
<provides>
|
|
|
|
<dev-mode>
|
|
|
|
<dev-mode>
|
|
|
|
<values>
|
|
|
|
<values>
|
|
|
|
<link>
|
|
|
|
<link>]
|
|
|
|
<test-start>]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@chunk[<req>
|
|
|
|
@chunk[<req>
|
|
|
|
(require
|
|
|
|
(require
|
|
|
@ -254,10 +253,9 @@ incorporates everything else already in the source file. Moreover, all of our `m
|
|
|
|
will be combined into a single submodule.
|
|
|
|
will be combined into a single submodule.
|
|
|
|
|
|
|
|
|
|
|
|
@chunk[<test-start>
|
|
|
|
@chunk[<test-start>
|
|
|
|
(error 'boing)
|
|
|
|
|
|
|
|
(module+ test
|
|
|
|
(module+ test
|
|
|
|
(require rackunit txexpr) ;; always include this at the start of the test submodule
|
|
|
|
(require rackunit txexpr) ;; always include this at the start of the test submodule
|
|
|
|
|
|
|
|
|
|
|
|
;; We use `check-txexprs-equal?` rather than `check-equal?` because it's a little more lenient:
|
|
|
|
;; We use `check-txexprs-equal?` rather than `check-equal?` because it's a little more lenient:
|
|
|
|
;; it allows the attributes of two txexprs to be in a different order,
|
|
|
|
;; it allows the attributes of two txexprs to be in a different order,
|
|
|
|
;; yet still be considered equal (because ordering of attributes is not semantically significant).
|
|
|
|
;; yet still be considered equal (because ordering of attributes is not semantically significant).
|
|
|
|