True and false booleans are represented by the values #t and #f, respectively, though operations that depend on a boolean value typically treat anything other than #f as true. The #t value is always eq? to itself, and #f is always eq? to itself.
Datatypes with further specification of equal? include strings, byte strings, pairs, mutable pairs, vectors, boxes, hash tables, and inspectable structures. In the last six cases, equality is recursively defined; if both v1 and v2 contain reference cycles, they are equal when the infinite unfoldings of the values would be equal. See also gen:equal+hash and prop:impersonator-of.
> (equal? 'yes 'yes)
> (equal? 'yes 'no)
> (equal? (expt 2 100) (expt 2 100))
> (equal? 2 2.0)
> (equal? (make-string 3 #\z) (make-string 3 #\z))
The number and character datatypes are the only ones for
which eqv? differs from eq?. Two numbers are
eqv? when they have the same exactness, precision, and are
both equal and non-zero, both 0.0, both 0.0f0, both
-0.0, both -0.0f0, both +nan.0, or both
> (eqv? 'yes 'yes)
> (eqv? 'yes 'no)
> (eqv? (expt 2 100) (expt 2 100))
> (eqv? 2 2.0)
> (eqv? (integer->char 955) (integer->char 955))
> (eqv? (make-string 3 #\z) (make-string 3 #\z))
> (equal?/recur 1 1 (lambda (a b) #f))
> (equal?/recur '(1) '(1) (lambda (a b) #f))
> (equal?/recur '#(1 1 1) '#(1 1.2 3/4) (lambda (a b) (<= (abs (- a b)) 0.25)))
Note that immutable? is not a general predicate for
immutability (despite its name). It works only for a handful of
datatypes for which a single predicate—
> (immutable? 'hello)
> (immutable? "a string")
> (immutable? (box 5))
> (immutable? #(0 1 2 3))
> (immutable? (make-hash))
> (immutable? (make-immutable-hash '([a b])))
equal-proc : (-> any/c any/c (-> any/c any/c boolean?) any/c) —
tests whether the first two arguments are equal, where both values are instances of the structure type to which the generic interface is associated (or a subtype of the structure type).
The third argument is an equal? predicate to use for recursive equality checks; use the given predicate instead of equal? to ensure that data cycles are handled properly and to work with equal?/recur (but beware that an arbitrary function can be provided to equal?/recur for recursive checks, which means that arguments provided to the predicate might be exposed to arbitrary code).
The equal-proc is called for a pair of structures only when they are not eq?, and only when they both have a gen:equal+hash value inherited from the same structure type. With this strategy, the order in which equal? receives two structures does not matter. It also means that, by default, a structure sub-type inherits the equality predicate of its parent, if any.
hash-proc : (-> any/c (-> any/c exact-integer?) exact-integer?) —
computes a hash code for the given structure, like equal-hash-code. The first argument is an instance of the structure type (or one of its subtypes) to which the generic interface is associated.
The second argument is an equal-hash-code-like procedure to use for recursive hash-code computation; use the given procedure instead of equal-hash-code to ensure that data cycles are handled properly.
hash2-proc : (-> any/c (-> any/c exact-integer?) exact-integer?) —
computes a secondary hash code for the given structure. This procedure is like hash-proc, but analogous to equal-secondary-hash-code.
Take care to ensure that hash-proc and hash2-proc are consistent with equal-proc. Specifically, hash-proc and hash2-proc should produce the same value for any two structures for which equal-proc produces a true value.
When a structure type has no gen:equal+hash implementation, then transparent structures (i.e., structures with an inspector that is controlled by the current inspector) are equal? when they are instances of the same structure type (not counting sub-types), and when they have equal? field values. For transparent structures, equal-hash-code and equal-secondary-hash-code derive hash code using the field values. For opaque structure types, equal? is the same as eq?, and equal-hash-code and equal-secondary-hash-code results are based only on eq-hash-code. If a structure has a prop:impersonator-of property, then the prop:impersonator-of property takes precedence over gen:equal+hash if the property value’s procedure returns a non-#f value when applied to the structure.
> (define (farm=? farm1 farm2 recursive-equal?) (and (= (farm-apples farm1) (farm-apples farm2)) (= (farm-oranges farm1) (farm-oranges farm2)) (= (farm-sheep farm1) (farm-sheep farm2))))
> (define (farm-hash-1 farm recursive-equal-hash) (+ (* 10000 (farm-apples farm)) (* 100 (farm-oranges farm)) (* 1 (farm-sheep farm))))
> (define (farm-hash-2 farm recursive-equal-hash) (+ (* 10000 (farm-sheep farm)) (* 100 (farm-apples farm)) (* 1 (farm-oranges farm))))
> (define-struct farm (apples oranges sheep) #:methods gen:equal+hash [(define equal-proc farm=?) (define hash-proc farm-hash-1) (define hash2-proc farm-hash-2)])
> (define east (make-farm 5 2 20))
> (define west (make-farm 18 6 14))
> (define north (make-farm 5 20 20))
> (define south (make-farm 18 6 14))
> (equal? east west)
> (equal? east north)
> (equal? west south)
(nand expr ...)
(nor expr ...)
In the two argument case, returns #t if neither of the arguments is a true value.
(implies expr1 expr2)
Same as (if expr1 expr2 #t).
If exactly one of b1 and b2 is not #f, then return it. Otherwise, returns #f.