You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make an object property fully private. The closure method is not memory efficient, and not sure about JIT optimisations, but may be bad.
The symbol is a scope free way to index a private property on an object, the scope of the symbol instance beeing declared on the definition level and not a instanciation.
So real private is easy, but sharing protected symbols will be harder ... Question is still open.
The text was updated successfully, but these errors were encountered:
Take the same approach as TypeScript for protected values. For private values, as they are Class dependents, I'll find a way to avoid colisions between child/base classes (prefix with an arbitrary hash - low collision probability ?)
In order to make an object property fully private. The closure method is not memory efficient, and not sure about JIT optimisations, but may be bad.
The symbol is a scope free way to index a private property on an object, the scope of the symbol instance beeing declared on the definition level and not a instanciation.
So real private is easy, but sharing protected symbols will be harder ... Question is still open.
The text was updated successfully, but these errors were encountered: