# What to Do About FUNCT (including "Not Calling It That")

**URL:** <https://revolt.metaeducation.com/forum/t/what-to-do-about-funct-including-not-calling-it-that/1518>\
**Category:** Naming\
**Created:** [February 23, 2021, 3:44am UTC](https://revolt.metaeducation.com/forum/t/what-to-do-about-funct-including-not-calling-it-that/1518 "2021-02-23T03:44:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [December 25, 2025, 4:21am UTC](https://revolt.metaeducation.com/forum/t/what-to-do-about-funct-including-not-calling-it-that/1518/6 "2025-12-25T04:21:18Z")

</div>

> [@rgchris](#):
>
> To be clear, I don't know that I'd agree that _shallow_ gathering in **function** (as-had-been-presumed) is necessarily bad. I still don't think that I'd use it, but I don't see it as the worst option.

I think FENCE! provides a generic answer regarding _generalized shallow gathering_ (what we have called WRAP in the past), but better than WRAP as it can be captured literally by syntax:

[FENCE!'s Higher Calling: WRAP](https://revolt.metaeducation.com/forum/t/fence-s-higher-calling-wrap/2613)

Because FUNC(TION) takes its body by value and stores it for multiple evaluations, it is necessary to take a FENCE! literally, otherwise any locals created would be bound to a single object created at the time of FUNC creation. If FUNC is able to see the FENCE! then it can do the gather and fold it in with the frame, which seems the right answer.

> [@rgchris](#):
>
> I agree that deep gathering is bad for any of the reasons you've described.

The FENCE! seems to be a very solid solution--that matches your intuition--that gathering should not be deep by default, but it allows you to be granular and push deeper with more fences if you feel it is warranted.

Only the top-level fence has the problem of needing literal capture (as otherwise it would be wrapped once and then used for multiple function invocations with the same object). This liability solved via actually merging those top level fields into the locals of the frame becomes an asset for efficiency.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/what-to-do-about-funct-including-not-calling-it-that/1518)._
