# What Are Definitional Returns?

**URL:** <https://revolt.metaeducation.com/forum/t/what-are-definitional-returns/2191>\
**Category:** Functions\
**Tags:** best-of\
**Created:** [October 20, 2019, 4:00am UTC](https://revolt.metaeducation.com/forum/t/what-are-definitional-returns/2191 "2019-10-20T04:00:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 8, 2025, 7:54pm UTC](https://revolt.metaeducation.com/forum/t/what-are-definitional-returns/2191/2 "2025-11-08T19:54:24Z")

</div>

> [@hostilefork](#):
>
> **I maintain that correct behavior constitutes another must-have, [and I was by no means alone in this, nor the first to say so](https://github.com/metaeducation/rebol-issues/issues/539#issuecomment-170878011)**.

Worth noting is [there's an issue in the Red repository for this as well](https://github.com/red/red/issues/4416#issuecomment-811786089):

Says @hiiamboris:

> _"Maybe crazy: bind every `return` & `exit` the same way we do bind function arguments/locals, so that they know their scope from the context they are bound to. But then if we write `code: [return 1] f: does [do code]` it won't work. Trading one limitation for another, plus likely more complexity in interpreter code. And we can't bind `break`/`continue` as there is no context for loops..."_

_**["That’s not extremism; that’s epistemic hygiene."](https://revolt.metaeducation.com/forum/t/my-summary-of-the-big-picture/1792/6)**_

I'll point out that in Revolt you _don't_ trade one limitation for another, because [binding propagates from tips of lists downward in evaluation](https://revolt.metaeducation.com/forum/t/rebol-and-scopes-well-why-not/1751), giving unbound material meaning as it descends. So unless you explicitly bound a RETURN word in a block, it will get its meaning from context, even if definitional.

Making return able to not take an argument (`func [...] [if ... [return] ...]`) avoids needing a separate definitional EXIT. Also, it's nice to retake the word EXIT for other things.

And of course, [Revolt has definitional BREAK and CONTINUE](https://revolt.metaeducation.com/forum/t/definitional-break-and-continue-the-time-is-now/2066) _(as well as definitional THROW, where you can also pass CATCH the word to use as its "throw")_

So not crazy at all, if you have the right binding ideas.

> "plus likely more complexity in interpreter code."

Simple but broken is not actually simple. It's just...broken.

_"everything should be made as simple as possible, but no simpler"_

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/what-are-definitional-returns/2191)._
