@Adnan @Mr.Xcoder I'm probably missing all kind of edge cases, but let's say you have two 1-byters, one to save a function and one to load a function (i.e. f and g). f would then be in the form: fCODE} (or perhaps fCODEf similar to quotes), where the CODE part is just saved as a string somewhere. And then when the function is used again with g it will internally call the same code as .V (interpret as 05AB1E code).

But again, I'm probably missing all kind of edge cases with this approach. And I'm not sure if functions would be good for this 05AB1E v2 release, but perhaps something for the future?

@Mr.Xcoder I guess you're thinking about something similar as Links in Jelly?

Precisely.

@KevinCruijssen That's similar to what I was thinking of too.

But I guess workarounds with .V would also work.

@Mr.Xcoder Yeah of course. You can always save a string yourself and use it multiple times with .V I guess. ;)

On the other hand, I've done a few challenges in 05AB1E where I had to do the same thing multiple times and because 05AB1E doesn't has any functions I thought about it differently and was still able to solve it. Can't really think of an example now. But my point is that lack of functions in 05AB1E might also be a strength, forcing you to think of a different solution in some cases.

FWIW, I didn't know .V existed until after I made that proposal.

@Mr.Xcoder :) It's actually quite useful. I especially like the way @Adnan used it today in combination with ÿ here: codegolf.stackexchange.com/a/170323/52210