Phill

there isnt an implementation for that, a workaround is to write it like ```cs Ray ray; Gizmos.DrawLine(ray.point, ray.point + ray.direction); ``` if the package is added as an embedded package,...

i can try but i cant guarantee ill do it :p, if you find a solution to the root cause i can review the pr with you (theres likely areas...

i could see it becoming an array rented from `ArrayPool.Shared` and then returned after being used/consumed after drawing, trying to figure out why it wasnt like that in the beginning...

is this issue still open for real? is it something that is still looked into/thought about? or has it been thrown under the rug? @tannergooding > it is highly unlikely...

Mine and others reasoning is to use a data type that is more appropriate with the constraints. If the argument was for how much larger a stackalloc could be as...

i agree with @erdemserhatergen and #26, but its already been put in place so yes technically it will break compatibility. but these types didnt need to be written as included...