From 471ef9b710f88765d871ab079f8485ba0268201d Mon Sep 17 00:00:00 2001 From: Kimplul Date: Thu, 5 Dec 2024 13:39:31 +0200 Subject: add note about functions as expressions --- README.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/README.md b/README.md index 4191246..2bf5588 100644 --- a/README.md +++ b/README.md @@ -118,3 +118,34 @@ allowing recursion. We might even want to require that a function can be turned into a 'returning' function (being pretentious we might prefer calling it 'folding' but anyway) so that it can be interfaced from C code, for example. + +### Function calls as arguments + +At the moment, it's a bit cumbersome to directly pass closure arguments to other +functions: +``` +get_some_value() => n; +do_something_with(n) => ... +``` + +If we don't really care about the named variable `n`, it might make more sense +to provide syntactic sugar like +``` +do_something_with(get_some_value()) => ... +``` + +that translates to the same thing as above, with some internal variable 'name'. +This would also require that `get_some_value` has some limitations, like a +single closure argument that consists of a single value. This might be +particularly significant for condition checking, like +``` +// assuming this is the form of if statements, as they're still not in the +// grammar +get_some_value() => cond; +if cond {...} +``` + +versus +``` +if get_some_value () {...} +``` -- cgit v1.2.3