Todd Fleming

The workaround above is incomplete. Not declaring the `gt, ge, lt, le, first, last, before, after` arguments and passing `{}` instead disables paging.

There will always be a point where shortcuts don't cover a common use case, so the full machinery must be explicitly invoked. Have we reached a limit yet? I don't...

I just had an idea which could remove some of the pain. This use of macros feels icky though. ``` #define MACRO_1(T) \ std::optional gt, \ std::optional ge, \ ......

Agreed

jscut's core algorithms are polygon manipulation algorithms; they can't handle open paths.