locationtech / locationtech/jts
Respect Thread interruption in potentially long-running loops.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.2k
- Forks
- 475
- Avg merge
- 14d 10h
- Merged PRs (30d)
- 1
Description
JTS operations that take a long time aren't cancellable; there's no way to signal to JTS that we no longer care about the result. For long-running operations on gigantic polygons in RobustLineIntersector and MCIndexNoder, for example, it'd be nice if we were good Java citizens and checked for Thread interruption or provided some other flag for cooperative cancellation.
Contributor guide
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.
Research direction
Start by reading the long-running loops in RobustLineIntersector and MCIndexNoder and tracing the operations that reach them. Determine whether Thread interruption or another cooperative-cancellation signal can cover both examples, and verify that cancellation prevents the operation from continuing to completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100