prisma-risk / tsoracle / 26492944394

95%

push

github

refactor(core): use WindowGrant::new_unchecked in try_grant hot path (#564)

The Allocator::try_grant call site previously routed through
WindowGrant::try_new even though project_grant has already proved every
bound try_new re-checks (count != 0, physical_ms <= PHYSICAL_MS_MAX,
logical range fits LOGICAL_MAX). On this #[PerformanceCriticalPath] that
meant four checked operations and a dead error path on every successful
grant. The block comment at the call site explicitly named the checks
as redundant.

Add a pub(crate) WindowGrant::new_unchecked that constructs the grant
directly, with debug_assert!s mirroring project_grant's bounds so a
future drift between the two trips loudly in test builds at zero release
cost. The public API still has only one validating constructor; the
back door is gated to the crate and documents the same invariant as a
caller obligation.

Signed-off-by: Sebastian Thiebaud <sebastian@prismarisk.com>

17 of 17 new or added lines in 1 file covered. (100.0%)

14184 of 14945 relevant lines covered (94.91%)

383175.53 hits per line