# Meet VETO: The VETO-in-NULL-out Protocol

**URL:** <https://revolt.metaeducation.com/forum/t/meet-veto-the-veto-in-null-out-protocol/1880>\
**Category:** Errors\
**Created:** [July 14, 2022, 4:21am UTC](https://revolt.metaeducation.com/forum/t/meet-veto-the-veto-in-null-out-protocol/1880 "2022-07-14T04:21:12Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [January 28, 2026, 3:13pm UTC](https://revolt.metaeducation.com/forum/t/meet-veto-the-veto-in-null-out-protocol/1880/11 "2026-01-28T15:13:08Z")

</div>

> [@All-SPLICE!: REDUCE, DELIMIT (SPACED, MOLD...)](https://revolt.metaeducation.com/forum/t/all-splice-reduce-delimit-spaced-mold/1917/4):
>
> ```plaintext
> keep opt compose ~[
> return: (conditional ret.spec)
> ]~
> 
> ```

I'll point this out as an _interesting_--although misguided---use of `~(veto)~`

It implements the same intent as:

```
if ret.spec [
    keep compose ~[
        return: (ret.spec)
    ]~
]

```

But it's clearer with the IF... and also avoids unnecessary computation (why call COMPOSE at all, and have it start building a stack it's going to throw away?)

So I'm going to change it...

..BUT _sometimes_ you just want the code to be structured differently. If I were in a situation where adding control _outside_ would be disruptive, I can put the control _inside_. Cool to have that ability.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/meet-veto-the-veto-in-null-out-protocol/1880)._
