alteredq/three.js — comment on commit baf0f65e1db76cc95e3d1a3cf759861b807fa177
File:  line 0
By ekitson:

Hi, I was browsing the commit list and noticed this conversation. I had a thought, if the API was changed from:

`Vector3.relativeToAbsolute( Object3D )`
`Vector3.absoluteToRelative( Object3D )`

to:

`Object3D.relativeToAbsolute( Vector3 )`
`Object3D.absoluteToRelative( Vector3 )`

maybe you could avoid this issue? This would explicitly imply that the Vector3 being passed in is mutated and then the user could decide if they need to create a new Vector3 or pass in an existing one rather than the library trying to decide if it should. Another option could even be:

`Matrix4.relativeToAbsolute( Vector3 )`
`Matrix4.absoluteToRelative( Vector3 )`

which would allow finer grained control. The user could decide if they want to use an Object3D's local matrix or world matrix. Just some thoughts!