Optimize and clarify closest-point computation in BoundaryCheck
All threads resolved!
All threads resolved!
It feels like compilers should be smarter sometimes... but a ~3x speedup on failing boundary checks with tolerances is nothing to snide at.
Merge request reports
Activity
Filter activity
- Resolved by Hadrien Benjamin Grasland
The incremental build fails because on your fork, the highest tag it selects as a baseline is
v0.3.0
added 31 commits
-
aa33a211...917eb8ff - 30 commits from branch
acts:master
- cbae60fb - Optimize closest-point computation in BoundaryCheck
-
aa33a211...917eb8ff - 30 commits from branch
changed milestone to %0.15.00
added Improvement label
enabled an automatic merge when the pipeline for cbae60fb succeeds
added Approved label
mentioned in commit b5d57286
Please register or sign in to reply