{"action":"opened","issue":{"url":"https://api.github.com/repos/rust-lang/rust/issues/21084","labels_url":"https://api.github.com/repos/rust-lang/rust/issues/21084/labels{/name}","comments_url":"https://api.github.com/repos/rust-lang/rust/issues/21084/comments","events_url":"https://api.github.com/repos/rust-lang/rust/issues/21084/events","html_url":"https://github.com/rust-lang/rust/issues/21084","id":54171847,"number":21084,"title":"Revert #[warn(unstable)] by default","user":{"login":"SimonSapin","id":291359,"avatar_url":"https://avatars.githubusercontent.com/u/291359?v=3","gravatar_id":"","url":"https://api.github.com/users/SimonSapin","html_url":"https://github.com/SimonSapin","followers_url":"https://api.github.com/users/SimonSapin/followers","following_url":"https://api.github.com/users/SimonSapin/following{/other_user}","gists_url":"https://api.github.com/users/SimonSapin/gists{/gist_id}","starred_url":"https://api.github.com/users/SimonSapin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SimonSapin/subscriptions","organizations_url":"https://api.github.com/users/SimonSapin/orgs","repos_url":"https://api.github.com/users/SimonSapin/repos","events_url":"https://api.github.com/users/SimonSapin/events{/privacy}","received_events_url":"https://api.github.com/users/SimonSapin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-13T10:11:44Z","updated_at":"2015-01-13T10:11:44Z","closed_at":null,"body":"One of the changes introduced by f3b67afcab9293faf77aafeaccfdda19e5a08d38 is:\r\n> * On the nightly channel, use of unstable APIs generates a warning.\r\n\r\nI think this should be reverted for now. Here is why:\r\n\r\nA warning is only useful when it is actionable. “You should not do this” is ideally accompanied by “do that instead”. Maintainers fix their code and the warning goes away. But this is not the case of most unstable warnings, there is not stable equivalent of the functionality. Therefore, in order to see the few actionable warnings, maintainers are lead to add `#![allow(unstable)]` to their crates. This is not great, because they (or at least I) are likely to forget to remove it when unstable warnings become useful.\r\n\r\nCC @alexcrichton "}}