Reduce the nesting depth for input validation by defining rejects as tag functions rather than traditional wrappers.
Security Considerations
n/a
Scaling Considerations
Constructing details is already in the slow path exercised only with an explicit check function, and introducing rest/spread to the wrapper imposes minor additional cost (the reject call itself gets about 6% slower on XS and 20% slower on V8). We could probably do better by passing reject functions rather than constructing them at each level, but that would affect the public API so I'm not contemplating that here.
Documentation Considerations
n/a
Testing Considerations
n/a
Compatibility Considerations
n/a
Upgrade Considerations
n/a
[ ] Includes *BREAKING*: in the commit message with migration instructions for any breaking change.
Description
Reduce the nesting depth for input validation by defining
rejects as tag functions rather than traditional wrappers.Security Considerations
n/a
Scaling Considerations
Constructing details is already in the slow path exercised only with an explicit check function, and introducing rest/spread to the wrapper imposes minor additional cost (the
rejectcall itself gets about 6% slower on XS and 20% slower on V8). We could probably do better by passingrejectfunctions rather than constructing them at each level, but that would affect the public API so I'm not contemplating that here.Documentation Considerations
n/a
Testing Considerations
n/a
Compatibility Considerations
n/a
Upgrade Considerations
n/a
Includes*BREAKING*:in the commit message with migration instructions for any breaking change.UpdatesNEWS.mdfor user-facing changes.