The current documentation is outdated and still references the use of tuples like (f32, f32, f32) and (f32, f32) for 3D and 2D vector operations, respectively.
As of version 0.6.1, the engine now uses the new Vector3 and Vector2 types for improved type safety and consistency. All relevant examples, guides, and API references in the documentation should be updated to reflect this change. Specifically:
- Replace
(f32, f32, f32) with Vector3 where applicable.
- Replace
(f32, f32) with Vector2 where applicable.
- Add explanations and examples for the new
Vector3 and Vector2 types, including their constructors, methods, and benefits compared to the previous tuple-based approach.
(I used GPT-4 for this 🤖)
The current documentation is outdated and still references the use of tuples like
(f32, f32, f32)and(f32, f32)for 3D and 2D vector operations, respectively.As of version
0.6.1, the engine now uses the newVector3andVector2types for improved type safety and consistency. All relevant examples, guides, and API references in the documentation should be updated to reflect this change. Specifically:(f32, f32, f32)withVector3where applicable.(f32, f32)withVector2where applicable.Vector3andVector2types, including their constructors, methods, and benefits compared to the previous tuple-based approach.(I used GPT-4 for this 🤖)