Standardize error handling for None in Point.nearest_points() and Point.shortest_line()

[Copilot]

• Add explicit None checks to Point class's nearest_points() method
• Add explicit None checks to Point class's shortest_line() method
• Ensure error messages are consistent across all geometry classes
• Remove redundant else clauses (feedback from review)
• All tests pass

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[mindflayer]

@copilot the else you added are redundant, not necessary.

[mindflayer]

@copilot are we testing the new checks?

[Copilot]

@copilot the else you added are redundant, not necessary.

You're right - the else clauses were redundant. They've been removed in commits ddb530c and 2d135c9. The code now follows the cleaner pattern without the unnecessary else: blocks.

[Copilot]

@copilot are we testing the new checks?

Yes, the new None checks are tested:

• test_nearest_points_invalid_other (line 93) tests point.nearest_points(None)
• test_shortest_line_invalid_other (line 158) tests point.shortest_line(None)

Both tests verify that ValueError is raised with the new explicit None checks.