{"action":"opened","issue":{"url":"https://api.github.com/repos/Sparrow-lang/future-work/issues/32","repository_url":"https://api.github.com/repos/Sparrow-lang/future-work","labels_url":"https://api.github.com/repos/Sparrow-lang/future-work/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/Sparrow-lang/future-work/issues/32/comments","events_url":"https://api.github.com/repos/Sparrow-lang/future-work/issues/32/events","html_url":"https://github.com/Sparrow-lang/future-work/issues/32","id":298112813,"number":32,"title":"Profile guided data-struct assistant","user":{"login":"lucteo","id":9896706,"avatar_url":"https://avatars0.githubusercontent.com/u/9896706?v=4","gravatar_id":"","url":"https://api.github.com/users/lucteo","html_url":"https://github.com/lucteo","followers_url":"https://api.github.com/users/lucteo/followers","following_url":"https://api.github.com/users/lucteo/following{/other_user}","gists_url":"https://api.github.com/users/lucteo/gists{/gist_id}","starred_url":"https://api.github.com/users/lucteo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lucteo/subscriptions","organizations_url":"https://api.github.com/users/lucteo/orgs","repos_url":"https://api.github.com/users/lucteo/repos","events_url":"https://api.github.com/users/lucteo/events{/privacy}","received_events_url":"https://api.github.com/users/lucteo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-18T19:56:39Z","updated_at":"2018-02-18T19:56:39Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Imagine a data structure containing a list. Wouldn't it be nice if the compiler could suggest to you to replace that data structure with a vector, a dequeue, a small vector or something else, based on your usage?\r\n\r\nWe would want to have a profile-guided query of what the program is actually using, then feed this into a compile-time module that can make suggestions to the choice of datastructures used.\r\n\r\nThis is somehow similar to #30, as it attempts to make performance-related decisions at compile-time. However the goal and the way it works is completely independent.\r\nAlso, this is somehow similar to #10, where the compile-time checker generates warnings for certain usage patterns; however, in this case we are considering performance as the main target, not necessarily safety. Both this proposal and #10 can be implemented on a common framework."}}
{"actor":{"display_login":"lucteo"}}