{"action":"opened","issue":{"url":"https://api.github.com/repos/Microsoft/cpprestsdk/issues/785","repository_url":"https://api.github.com/repos/Microsoft/cpprestsdk","labels_url":"https://api.github.com/repos/Microsoft/cpprestsdk/issues/785/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/cpprestsdk/issues/785/comments","events_url":"https://api.github.com/repos/Microsoft/cpprestsdk/issues/785/events","html_url":"https://github.com/Microsoft/cpprestsdk/issues/785","id":331994651,"node_id":"MDU6SXNzdWUzMzE5OTQ2NTE=","number":785,"title":"PPLx without exceptions","user":{"login":"jfrsmith","id":962442,"node_id":"MDQ6VXNlcjk2MjQ0Mg==","avatar_url":"https://avatars3.githubusercontent.com/u/962442?v=4","gravatar_id":"","url":"https://api.github.com/users/jfrsmith","html_url":"https://github.com/jfrsmith","followers_url":"https://api.github.com/users/jfrsmith/followers","following_url":"https://api.github.com/users/jfrsmith/following{/other_user}","gists_url":"https://api.github.com/users/jfrsmith/gists{/gist_id}","starred_url":"https://api.github.com/users/jfrsmith/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jfrsmith/subscriptions","organizations_url":"https://api.github.com/users/jfrsmith/orgs","repos_url":"https://api.github.com/users/jfrsmith/repos","events_url":"https://api.github.com/users/jfrsmith/events{/privacy}","received_events_url":"https://api.github.com/users/jfrsmith/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-13T13:27:54Z","updated_at":"2018-06-13T13:27:54Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\n\r\nI'd like to use PPLx (not the entirity of cpprestsdk) within a project that targets platforms where exceptions are not enabled, but obviously the extent to which they're used within PPLx is considerable.\r\n\r\nI'd like to move towards exposing a [_expected_](http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0323r1.pdf)-based interface from tasks rather than exceptions, and was wondering if you had any suggestions about:\r\n\r\na) whether this is even remotely possible given the architecture of PPLx\r\nb) if it's _possible_, what broad level tasks would you suggest undertaking to migrate away from exceptions\r\n\r\nFor the purposes of this case, we can assume that no code running within a pplx::task would ever throw an exception.\r\n\r\nThanks,\r\nJack"}}
{"actor":{"display_login":"jfrsmith"}}