realiseContext: Remove no-op replacements

A possible use of them might have been to figure out the paths
(which can now be retrieved with maybePathsOut), but I have
not found evidence that it was used this way, and it would have
been broken, because non-CA outputs weren't recorded in the map.
This commit is contained in:
Robert Hensing 2024-04-05 16:15:43 +02:00
parent 02c41aba5b
commit c145ce0e1a

View file

@ -59,7 +59,6 @@ StringMap EvalState::realiseContext(const NixStringContext & context, StorePathS
}, },
[&](const NixStringContextElem::Opaque & o) { [&](const NixStringContextElem::Opaque & o) {
auto ctxS = store->printStorePath(o.path); auto ctxS = store->printStorePath(o.path);
res.insert_or_assign(ctxS, ctxS);
ensureValid(o.path); ensureValid(o.path);
if (maybePathsOut) if (maybePathsOut)
maybePathsOut->emplace(o.path); maybePathsOut->emplace(o.path);
@ -67,7 +66,6 @@ StringMap EvalState::realiseContext(const NixStringContext & context, StorePathS
[&](const NixStringContextElem::DrvDeep & d) { [&](const NixStringContextElem::DrvDeep & d) {
/* Treat same as Opaque */ /* Treat same as Opaque */
auto ctxS = store->printStorePath(d.drvPath); auto ctxS = store->printStorePath(d.drvPath);
res.insert_or_assign(ctxS, ctxS);
ensureValid(d.drvPath); ensureValid(d.drvPath);
if (maybePathsOut) if (maybePathsOut)
maybePathsOut->emplace(d.drvPath); maybePathsOut->emplace(d.drvPath);