Nicolas Silva

`Scale2D` and `Scale3D` would make sense.

No particular reason (I didn't know a restriction had been lifted).

It's still not quite clear to me how to implement this. Do you want to give it a go ?

The strongly typed getters returning `Length` used to exist but were removed in part because their names weren't very ergonomic (`foo.width_typed()`) and more importantly becaused it seemed that nobody used...

There are a few other getters to add but I'd like to discuss the naming scheme before doing the rest of the work.

For reference, I tinkered in a [separate branch](https://github.com/nical/euclid/commit/d12fce80356cba0f42348250b8c1ddfcc9e9c996) with another naming scheme that avoids the `get_` prefix: - `length()` and other methods that return distances/length-like semantic values return a `Length`...

I'm still keen on adding strongly typed variants of methods that return scalars where it makes sense using the `get_*` prefix. @kvark are you on board with it?

In practice we found out that people often don't use the units much when dealing with the scalar values (while they do with vectors and other types), so we want...

Note that you can write `let r = rect(x, y, w, h);` as a shorthand to create rects instead of `Rect::new` which is indeed cumbersome. I think that it is...

See: https://docs.rs/euclid/0.17.2/euclid/fn.rect.html it's a simple function that just calls `TypedRect::new(...)`. There are equivalent functions `point2`, `point3`, `size2`, `vec2`, etc.