Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Normative: Use own properties for privateName objects
This patch changes PrivateName objects to have a null prototype and own methods, as described in #68 (comment) I'm not sure whether we want to do the change, but I'm writing it up so that we can think more carefully about whether we want to go in this direction. This patch is the most concrete, reasonable thing I can imagine in the direction of more integrity. It's also a relatively small change vs the previous proposal. Some results of the change: - It's not possible to effectively monkey-patch anything in particular to intercept private name accesses; you can only change one in particular which you already have access to. - There may be slightly more memory consuption due to the privateName objects having more own properties, but not that much, as the methods remain not bound to the receiver. Closes #68
- Loading branch information
Showing
1 changed file
with
42 additions
and
83 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters