Double precision support for all fundamental geometry classes (PShape, PVector ...)

Relevant sub-area for this feature?

Core/Environment/Rendering

Feature description

When using PShape and PVector calculations alongside with native Path2D.Double objects (using various conversions) there are obvious, randomly appeared but systematic rendering artifacts - rounding errors (same result when using same parameter values) upon all kinds of calculations, transformations etc. With all that CPU processing power around, I guess there is no practical reason of not adding Double coordinate support for all classes without braking compatibility with existing projects.

Benefits

Use PShape and PVector classes alongside with other classes that support natively double precision coordinates like Path2D without precision errors. Future proof Processing projects.

Possible challenges

I do not have a clue what might be the impact in codebase. I guess there should be a compatibility code care for all existing projects and default will be Float.

Additional context

An Article about the precision artifacts: https://blog.generativedarkroom.com/why-i-switched-from-processing-to-openrndr-b50c931d21ae

首先检查 PShape 和 PVector 类，并将它们的坐标和计算路径与原生 Path2D.Double 对象进行比较。确定基础几何类中双精度支持的范围，以及如何保持与现有基于 float 的项目的兼容性；完成标准是达成一致的设计，并在没有报告中的渲染伪影的情况下保持一致的精度行为。