Tests that require debug assertions?

[rsheeter]

Import into google3 for 0.11.1 failed due to the following tests not working without debug assertions:

1. bezpath::tests::test_elements_to_segments_starts_on_closepath
2. bezpath::tests::test_must_not_start_on_quad

I can fix it by enabling debug assertions but ... do we really want to test behavior that doesn't occur in release?

[xStrom]

We should probably conditionally compile these tests only when debug_assertions is enabled as they depend on that being the case.

[DJMcNab]

You can conditionally #[ignore], which has better UX (displays a reason whilst running). But yes, that's the general shape of the solution.

do we really want to test behavior that doesn't occur in release?

If you're running the tests, you should have debug_assertions enabled to get the correct results. We're validating that sanity check debug assertions work; these are likely to be too expensive for hot loops using Kurbo (?), but are useful to catch mistakes.
But I've not looked into the details of these exact tests.