{"comment":{"url":"https://api.github.com/repos/CaseyCarter/stl2/comments/11802251","html_url":"https://github.com/CaseyCarter/stl2/commit/2d54e6b6275c9d1f97b3c5d899171ef53ef5dc04#commitcomment-11802251","id":11802251,"user":{"login":"ericniebler","id":225757,"avatar_url":"https://avatars.githubusercontent.com/u/225757?v=3","gravatar_id":"","url":"https://api.github.com/users/ericniebler","html_url":"https://github.com/ericniebler","followers_url":"https://api.github.com/users/ericniebler/followers","following_url":"https://api.github.com/users/ericniebler/following{/other_user}","gists_url":"https://api.github.com/users/ericniebler/gists{/gist_id}","starred_url":"https://api.github.com/users/ericniebler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ericniebler/subscriptions","organizations_url":"https://api.github.com/users/ericniebler/orgs","repos_url":"https://api.github.com/users/ericniebler/repos","events_url":"https://api.github.com/users/ericniebler/events{/privacy}","received_events_url":"https://api.github.com/users/ericniebler/received_events","type":"User","site_admin":false},"position":398,"line":743,"path":"concepts.tex","commit_id":"2d54e6b6275c9d1f97b3c5d899171ef53ef5dc04","created_at":"2015-06-22T19:58:00Z","updated_at":"2015-06-22T19:58:00Z","body":"There is no law against default constructible proxies. And the Palo Alto\nreport does not tie Copyable to value semantics, nor does it say that\nCopyable types are default constructible. I see no conflict in what I am\nsuggesting and n3351.\n\nOn Mon, Jun 22, 2015, 12:52 PM Casey Carter <notifications@github.com>\nwrote:\n\n> Proxies are absolutely CopyConstructible.\n>\n> IIUC, you are suggesting a different design than both mine and N3351's, in\n> which Copyable relaxes the \"value-semantic object\" requirements as well\n> as the default construction requirements of Semiregular in order to admit\n> types with reference semantics. Without having fully considered the\n> ramifications of that relaxation, my intuition is that we'd be better\n> served by characterizing the behavior of reference-semantic types with\n> separate concepts so that we have two distinct families with strong\n> requirements than can be combined when we want to allow either behavior (a\n> la Initializable) than to have one family of concepts with requirements\n> weak enough to admit both behaviors. I'll give it some more thought.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/CaseyCarter/stl2/commit/2d54e6b6275c9d1f97b3c5d899171ef53ef5dc04#commitcomment-11802163>\n> .\n>\n"}}