# Handling MATCH and "Falsey" Types

**URL:** <https://revolt.metaeducation.com/forum/t/handling-match-and-falsey-types/2080>\
**Category:** Semantics\
**Tags:** best-of\
**Created:** [May 15, 2022, 8:44am UTC](https://revolt.metaeducation.com/forum/t/handling-match-and-falsey-types/2080 "2022-05-15T08:44:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [August 29, 2022, 3:56pm UTC](https://revolt.metaeducation.com/forum/t/handling-match-and-falsey-types/2080/4 "2022-08-29T15:56:45Z")

</div>

> [@IngoHohmann](#):
>
> one less case to worry about.

...aaaand...with **[Flexible Logic](https://revolt.metaeducation.com/forum/t/flexible-logic-system-terminology/2252)**.... **Now We Don't Have To Worry About FALSE (or NO, or OFF) Either!**

We're down to _just one_ "branch inhibitor": The **`~null~ antiform`** ([and maaaaybe ~NaN~](https://revolt.metaeducation.com/forum/t/isotopes-and-nan-not-a-number/2245))

So it seems the options are:

1. _Don't worry about it._ If you write **match [logic?] 1 = 2** you get back a **~null~** antiform and should you write an expression like **if (match [logic?] 1 = 2) [print "Match!]** you get what you deserve.

2. _Error on it,_ e.g. **`match [null?] null`** panics.

3. _Have a MATCH:RELAX variant._ Let plain **match** on null trigger an error and if you write **if match:relax ...** then you clearly know what you're doing, so it becomes like case (1).

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/handling-match-and-falsey-types/2080)._
