The method saddle_connections has a squared_length_bound argument.

While in technical terms working with a bound on the squared length
has advantages, the user expects the bound to be on the length.

Even the saddle connections examples page trips over this at:

• https://github.com/flatsurf/sage-flatsurf/blob/0.4.1/doc/examples/saddle_connections.md

with an example phrased as

We get a list of all saddle connections of length less than 10.

but which uses

sc_list = s.saddle_connections(10)

and so only goes up to squared length 10, i.e. up to length sqrt(10).

Ideally this method could use keyword arguments to offer a choice:

• max_length=0
• max_length_squared=0
• max_combinatorial_length=0

If several of them are provided, we could combine the constraints
(or raise an error). Combining the constraints would allow to bound
both the combinatorial and geometric length in dilation surfaces.

The main advantage of using squared length is to avoid taking
square roots, but we can avoid it anyway by checking whether
a^2 + b^2 < c^2 instead of checking whether sqrt(a^2 + b^2) < c.

It would also be nice to allow users to specify whether to use
<= or < when checking against the provided bound.