{"action":"closed","issue":{"url":"https://api.github.com/repos/rust-lang/rust-playpen/issues/154","repository_url":"https://api.github.com/repos/rust-lang/rust-playpen","labels_url":"https://api.github.com/repos/rust-lang/rust-playpen/issues/154/labels{/name}","comments_url":"https://api.github.com/repos/rust-lang/rust-playpen/issues/154/comments","events_url":"https://api.github.com/repos/rust-lang/rust-playpen/issues/154/events","html_url":"https://github.com/rust-lang/rust-playpen/issues/154","id":117348036,"number":154,"title":"Add an option to show the MIR","user":{"login":"RalfJung","id":330628,"avatar_url":"https://avatars.githubusercontent.com/u/330628?v=3","gravatar_id":"","url":"https://api.github.com/users/RalfJung","html_url":"https://github.com/RalfJung","followers_url":"https://api.github.com/users/RalfJung/followers","following_url":"https://api.github.com/users/RalfJung/following{/other_user}","gists_url":"https://api.github.com/users/RalfJung/gists{/gist_id}","starred_url":"https://api.github.com/users/RalfJung/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RalfJung/subscriptions","organizations_url":"https://api.github.com/users/RalfJung/orgs","repos_url":"https://api.github.com/users/RalfJung/repos","events_url":"https://api.github.com/users/RalfJung/events{/privacy}","received_events_url":"https://api.github.com/users/RalfJung/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-17T12:45:21Z","updated_at":"2016-02-19T06:52:47Z","closed_at":"2016-02-19T06:52:47Z","body":"I think it would be awesome if Rust Playpen could display the MIR of the code - that is, the MIR generated for every single function, and (potentially) the tables that are kept around, storing information about types. (I know very little about what information is actually kept around besides the MIR code itself.)\r\n\r\nWith the MIR becoming a central piece of the compiler, and borrow checking determined to be performed on the MIR eventually, I think this will be a great tool to debug borrowck issues, and to learn more about what happens \"behind the scenes\", about all the desugaring that's going on. The LLVM IR is so low-level that much of this can't be seen anymore."}}