Commit d84304d
committed
load_or_install: trust load() result when no_cache is set
Devin Review caught that ``if loaded.is_valid and not no_cache:`` applied the
caller's ``no_cache`` flag to the value we just got back from ``load()``.
``load()`` already honours the flag internally, so a valid result is fresh
regardless — the ``and not no_cache`` guard was forcing a redundant
``install()`` whenever ``no_cache=True`` even though the binary already
resolved. Drop the redundant condition.1 parent c680d90 commit d84304d
1 file changed
+3
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
473 | 473 | | |
474 | 474 | | |
475 | 475 | | |
476 | | - | |
| 476 | + | |
| 477 | + | |
| 478 | + | |
477 | 479 | | |
478 | 480 | | |
479 | 481 | | |
| |||
0 commit comments