max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-15 02:36:16 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

getDoc: Explain why we partially apply __functor

Browse source
This commit is contained in:
Robert Hensing 2024-08-26 16:15:13 +02:00 committed by GitHub
parent 72a4d1f52d
commit 77ddcbe12e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
src/libexpr/eval.cc
View file

@ -621,6 +621,11 @@ std::optional<EvalState::Doc> EvalState::getDoc(Value & v)
Value & functor = *v.attrs()->find(sFunctor)->value; Value & functor = *v.attrs()->find(sFunctor)->value;
Value * vp = &v; Value * vp = &v;
Value partiallyApplied; Value partiallyApplied;
// The first paramater is not user-provided, and may be
// handled by code that is opaque to the user, like lib.const = x: y: y;
// So preferably we show docs that are relevant to the
// "partially applied" function returned by e.g. `const`.
// We apply the first argument:
callFunction(functor, 1, &vp, partiallyApplied, noPos); callFunction(functor, 1, &vp, partiallyApplied, noPos);
auto _level = addCallDepth(noPos); auto _level = addCallDepth(noPos);
return getDoc(partiallyApplied); return getDoc(partiallyApplied);