# GROUP!-headed Dispatch Of Functions Via WORD! (?)

**URL:** <https://revolt.metaeducation.com/forum/t/group-headed-dispatch-of-functions-via-word/2548>\
**Category:** Functions\
**Created:** [October 24, 2025, 7:49am UTC](https://revolt.metaeducation.com/forum/t/group-headed-dispatch-of-functions-via-word/2548 "2025-10-24T07:49:12Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [October 24, 2025, 7:49am UTC](https://revolt.metaeducation.com/forum/t/group-headed-dispatch-of-functions-via-word/2548/1 "2025-10-24T07:49:13Z")

</div>

If we want to use a GROUP! to assign a variable, we do that via the variable's "name", e.g. a bound WORD!:

> [@GROUP! for refinements in function invocation: worth it?](https://revolt.metaeducation.com/forum/t/group-for-refinements-in-function-invocation-worth-it/1813/3):
>
> ```plaintext
> >> foo: null
> == ~null~ ; anti
> 
> >> var: $foo
> == foo
> 
> >> (var): 1020
> == 1020
> 
> >> foo
> == 1020
> 
> ```

But I noticed that to do a function, you have to do it by value of the function:

> [@GROUP! for refinements in function invocation: worth it?](https://revolt.metaeducation.com/forum/t/group-for-refinements-in-function-invocation-worth-it/1813/3):
>
> ```plaintext
> >> fn: append/
> 
> >> (fn/):dup [a b c] [d e] 2
> == [a b c [d e] [d e]]
> 
> ```

And if GROUP!-headed non-trivial chains are to be allowed, that seems it should work. (Maybe they shouldn't be allowed, and you should use APPLY?)

But if they're allowed, is there a good reason not to allow it by name in that case, as well?

```plaintext
>> fname: $append

>> (fname):dup [a b c] [d e] 2
== [a b c [d e] [d e]]

```

I actually tried that first, and it didn't work.

Answering this question is perhaps a general question of "do non-trivial CHAIN!s have meanings outside of functions in the default evaluator".

```
>> str: "Some string"

>> str:foo
== ??? ; always an error? Or might str:foo mean something?

```

I was toying with that idea a bit at one point, like if **str:length** might be a shorthand for **length of str**.

But I'm leaning that with the idea of [dialected function calls](https://revolt.metaeducation.com/forum/t/dialecting-function-calls-new-weird-powerful/2310), the concept that you can take for granted that what you're looking at is a function interpreting a chain of information seems pretty important.

If that's the case, I don't know that I see much harm in allowing functions by variable name. But it's not a high priority, just thought I'd mention it in its own thread vs. a tangent at the end of another one.
