From 47c9f73d3605c8f6088314ffd626822d66d148ea Mon Sep 17 00:00:00 2001 From: skye Date: Mon, 13 Apr 2026 16:34:43 -0400 Subject: [PATCH] doc/manual: Update signature of primop fn in hacking.md This should have been part of cl/5456, but I didn't notice it at the time. Change-Id: I3afe75c5862ecd3ce2f616a2ae30aff96a6a6964 --- doc/manual/src/contributing/hacking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manual/src/contributing/hacking.md b/doc/manual/src/contributing/hacking.md index 507fcbb59..ccc804b24 100644 --- a/doc/manual/src/contributing/hacking.md +++ b/doc/manual/src/contributing/hacking.md @@ -566,7 +566,7 @@ Then add the new file there, and don't forget to register it in the appropriate The following metadata properties are supported for builtin functions: * `name` (required): the language-facing name (as a member of the `builtins` attribute set) of the function. * `implementation` (optional): a C++ expression specifying the implementation of the builtin. - It must be a function of signature `void(EvalState &, PosIdx, Value * *, Value &)`. + It must be a function of signature `Value(EvalState &, PosIdx, Value * *)`. If not specified, defaults to `prim_${name}`. * `renameInGlobalScope` (optional): whether the definition should be "hidden" in the global scope by prefixing its name with two underscores. If not specified, defaults to `true`.