Make the use of ARRAY_BOUNDS_CHECK and LVARRAY_ASSERT consistent
@corbett5 is already working on this.
Since Jul 16, 2020.
Assessment
This issue has not been assessed yet.
Description
In the CRSMatrix::addToRow methods there are multiple uses of LVARRAY_ASSERT. These should probably be LVARRAY_ERROR and only enabled if ARRAY_BOUNDS_CHECK is on. Same thing in other places.
- Dominant language
- C++
- Stars
- 49
- Forks
- 9
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GEOS-DEV/LvArray
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
GPU stacktrace Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
All issues in GEOS-DEV/LvArray
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·