Skip to content

Scalar truncation is implemented over scalar values instead of scalars and can operate in place#6414

Open
robert3005 wants to merge 3 commits intodevelopfrom
rk/inplacetruncation
Open

Scalar truncation is implemented over scalar values instead of scalars and can operate in place#6414
robert3005 wants to merge 3 commits intodevelopfrom
rk/inplacetruncation

Conversation

@robert3005
Copy link
Contributor

@robert3005 robert3005 commented Feb 10, 2026

As a followup to the massive scalar refactor I have refactored the truncation logic to not require typed scalars. Since we now guarantee that values will be coerced to appropriate scalar value we can implement truncation logic over the underlying primitives

closes #6413

@robert3005 robert3005 added the changelog/chore A trivial change label Feb 10, 2026
@codspeed-hq
Copy link

codspeed-hq bot commented Feb 10, 2026

Merging this PR will not alter performance

✅ 1135 untouched benchmarks
⏩ 1268 skipped benchmarks1


Comparing rk/inplacetruncation (17406b8) with develop (66b85b7)

Open in CodSpeed

Footnotes

  1. 1268 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@robert3005 robert3005 requested a review from AdamGS February 12, 2026 16:39
@robert3005 robert3005 enabled auto-merge (squash) February 12, 2026 16:39
…s and can operate in place

Signed-off-by: Robert Kruszewski <github@robertk.io>
Signed-off-by: Robert Kruszewski <github@robertk.io>
Signed-off-by: Robert Kruszewski <github@robertk.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/chore A trivial change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lower and upper bound scalars

3 participants