New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace get/set functions with properties #1421
Comments
👍 As long as we are just replacing functions, we shouldn't notice a speed difference (on Chrome). Replacing public variables with properties (i.e. Cartesian3.x) would definitely still have an affect performance.I would advise whomever works on this to start by changing a single class (i.e. |
Firefox performance is comparable to functions when the properties are defined on the prototype (which is what we typically do anyway for memory reasons when replacing get/set functions). Properties on instances are still slow. FF bug: https://bugzilla.mozilla.org/show_bug.cgi?id=626021 |
All sounds good. No intention to change any public variables. |
@pjcozzi I think I've covered all of the major ones, which other files did you want changed over? |
Let's update the following types. They have trivial Since this will be a large change, it can be split into a few pull requests. Core:
Renderer (no need to add doc where it is
Scene:
DynamicScene will be updated separately so don't worry about files in that folder. Also, |
@hpinkos I changed the above list to checkboxes to make this a bit easier to track. |
Should be done throughout the API for consistency and to help stabilize it now that property access is fast.
For example:
will become
The text was updated successfully, but these errors were encountered: