Why not use Double? about svg-tree HOT 6 CLOSED

All visual rendering must be accurate to within one device pixel (px unit) to
the mathematically correct result at the initial 1:1 zoom ratio. It is suggested
that viewers attempt to keep a high degree of accuracy when zooming.

and

Both a Conforming High-Quality Static SVG Viewer and a Conforming
High-Quality Dynamic SVG Viewer must support the following additional
features:
...
At least double-precision floating point computation on coordinate system
transformation numerical calculations.

SkScalar of SKIA, the Chrome rendering library, which use float in it's pipeline.

Simply put, for rendering, float precision is sufficient. Thus said, holding all the geometry and transformation can be put in double, if it can open more use of the library. But changing the type of the drawing attributes hold literally no value.

And what is more problematic for me, it's a major change forcing a bump to a 0.3 version, that will force me to update rasterific-svg . I'm willing to accept a patch, if only transformation/geometry is switched to doubles.

from svg-tree.

What about _strokeWidth :: Number? That's a drawing attribute but is it OK to switch that to using Double since all the transformation/geometry uses the Number type as well?

from svg-tree.

I think we can, let's just keep only the color stuff with Float

from svg-tree.

So the problem I am running into in making this change as you describe is that the other attributes are tied to Number through the cssUniqueFloat and cssUniqueMayFloat lenses. I haven't had the time to understand whether these can be decoupled from Number in a nice way.

from svg-tree.

I've pulled your modifications and switched back the value for opacity, and bumped the revision number. is it good for you?

from svg-tree.

Yes, perfect, thanks very much! The ASetter type and the Lense operators were confusing me.

from svg-tree.