00f79da358
Refactor assertEq and assertThrows to be implemented in terms of a more generic assertBool to reduce code duplication and ease adding new assert types. To preserve meaningful error messages AssertResult is changed slightly: nope-eq and nope-throw have been replaced by a single nope branch which contains an AssertErrorContext which contains error information. To implement an assert assertBoolContext (which is not exposed) can be used: It takes an AssertErrorContext which is returned in case of an error and a boolean determining whether the assert was successful. The currently possible AssertErrorContext are: * should-throw: error result of assertThrows, formerly nope-throw * not-equal: error result of assertEq, formerly nope-eq Change-Id: Ifd6b3aa4187c90c3add2df63fa7c906c8f03fd2d Reviewed-on: https://cl.tvl.fyi/c/depot/+/2473 Tested-by: BuildkiteCI Reviewed-by: Profpatsch <mail@profpatsch.de> |
||
---|---|---|
.. | ||
binify | ||
bufCheck | ||
buildGo | ||
buildLisp | ||
emptyDerivation | ||
escapeExecline | ||
getBins | ||
mergePatch | ||
readTree | ||
runExecline | ||
runTestsuite | ||
tag | ||
tailscale | ||
writeElispBin | ||
writeExecline | ||
writeScript | ||
writeScriptBin | ||
yants | ||
OWNERS |