{"action":"created","issue":{"url":"https://api.github.com/repos/tc39/proposal-class-fields/issues/175","repository_url":"https://api.github.com/repos/tc39/proposal-class-fields","labels_url":"https://api.github.com/repos/tc39/proposal-class-fields/issues/175/labels{/name}","comments_url":"https://api.github.com/repos/tc39/proposal-class-fields/issues/175/comments","events_url":"https://api.github.com/repos/tc39/proposal-class-fields/issues/175/events","html_url":"https://github.com/tc39/proposal-class-fields/issues/175","id":383899522,"node_id":"MDU6SXNzdWUzODM4OTk1MjI=","number":175,"title":"Developer experience of the syntax and semantics of this proposal","user":{"login":"mbrowne","id":874316,"node_id":"MDQ6VXNlcjg3NDMxNg==","avatar_url":"https://avatars0.githubusercontent.com/u/874316?v=4","gravatar_id":"","url":"https://api.github.com/users/mbrowne","html_url":"https://github.com/mbrowne","followers_url":"https://api.github.com/users/mbrowne/followers","following_url":"https://api.github.com/users/mbrowne/following{/other_user}","gists_url":"https://api.github.com/users/mbrowne/gists{/gist_id}","starred_url":"https://api.github.com/users/mbrowne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbrowne/subscriptions","organizations_url":"https://api.github.com/users/mbrowne/orgs","repos_url":"https://api.github.com/users/mbrowne/repos","events_url":"https://api.github.com/users/mbrowne/events{/privacy}","received_events_url":"https://api.github.com/users/mbrowne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":37,"created_at":"2018-11-23T17:57:06Z","updated_at":"2018-11-25T20:44:15Z","closed_at":null,"author_association":"NONE","body":"This new issue is intended as a continuation of the recent discussion in #100. (The only reason for a new thread is that the original has become very, very long, which among other things makes it less approachable to anyone not already participating in the discussion.)\r\n\r\n**VERY IMPORTANT NOTE: Anyone who would like to comment here should first read the [PRIVATE SYNTAX FAQ](https://github.com/tc39/proposal-class-fields/blob/master/PRIVATE_SYNTAX_FAQ.md). This will save everyone time. Thank you.**"},"comment":{"url":"https://api.github.com/repos/tc39/proposal-class-fields/issues/comments/441471558","html_url":"https://github.com/tc39/proposal-class-fields/issues/175#issuecomment-441471558","issue_url":"https://api.github.com/repos/tc39/proposal-class-fields/issues/175","id":441471558,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MTQ3MTU1OA==","user":{"login":"SCLeoX","id":13428807,"node_id":"MDQ6VXNlcjEzNDI4ODA3","avatar_url":"https://avatars0.githubusercontent.com/u/13428807?v=4","gravatar_id":"","url":"https://api.github.com/users/SCLeoX","html_url":"https://github.com/SCLeoX","followers_url":"https://api.github.com/users/SCLeoX/followers","following_url":"https://api.github.com/users/SCLeoX/following{/other_user}","gists_url":"https://api.github.com/users/SCLeoX/gists{/gist_id}","starred_url":"https://api.github.com/users/SCLeoX/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SCLeoX/subscriptions","organizations_url":"https://api.github.com/users/SCLeoX/orgs","repos_url":"https://api.github.com/users/SCLeoX/repos","events_url":"https://api.github.com/users/SCLeoX/events{/privacy}","received_events_url":"https://api.github.com/users/SCLeoX/received_events","type":"User","site_admin":false},"created_at":"2018-11-25T20:44:15Z","updated_at":"2018-11-25T20:44:15Z","author_association":"NONE","body":"@mbrowne \r\n> What if the library author renamed or removed a private field in the process of reimplementing something to fix a bug, but otherwise the public API remained unchanged?\r\n\r\nThat's exactly why soft private is enough. Soft private can already prevent developers from using those private fields.  (Just to be clear, soft private = inaccessible but detectable)"}}
{"actor":{"display_login":"SCLeoX"}}