{"action":"opened","issue":{"url":"https://api.github.com/repos/alex/linux-kernel-module-rust/issues/41","repository_url":"https://api.github.com/repos/alex/linux-kernel-module-rust","labels_url":"https://api.github.com/repos/alex/linux-kernel-module-rust/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/alex/linux-kernel-module-rust/issues/41/comments","events_url":"https://api.github.com/repos/alex/linux-kernel-module-rust/issues/41/events","html_url":"https://github.com/alex/linux-kernel-module-rust/issues/41","id":328381035,"node_id":"MDU6SXNzdWUzMjgzODEwMzU=","number":41,"title":"Use stable Rust (tracking ticket for unstable features we use)","user":{"login":"geofft","id":74644,"node_id":"MDQ6VXNlcjc0NjQ0","avatar_url":"https://avatars1.githubusercontent.com/u/74644?v=4","gravatar_id":"","url":"https://api.github.com/users/geofft","html_url":"https://github.com/geofft","followers_url":"https://api.github.com/users/geofft/followers","following_url":"https://api.github.com/users/geofft/following{/other_user}","gists_url":"https://api.github.com/users/geofft/gists{/gist_id}","starred_url":"https://api.github.com/users/geofft/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geofft/subscriptions","organizations_url":"https://api.github.com/users/geofft/orgs","repos_url":"https://api.github.com/users/geofft/repos","events_url":"https://api.github.com/users/geofft/events{/privacy}","received_events_url":"https://api.github.com/users/geofft/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-01T04:48:12Z","updated_at":"2018-06-01T04:48:12Z","closed_at":null,"author_association":"COLLABORATOR","body":"More ambitious than #37, and won't be possible for a long while yet. Here's what we use currently:\r\n\r\n* `#![feature(alloc)]` to be able to use liballoc (`Box`, `String`, `Vec`, etc.). rust-lang/rust#27783 I think, though I don't see any recent progress about liballoc specifically. (But as noted in #37 most things we need are re-exported through libstd, so maybe we can advocate for pushing the unstable attribute down to the things that aren't re-exported?)\r\n* `#![feature(global_allocator)]` and `#![feature(allocator_api)]` to be able to define an allocator backed by printk. PR rust-lang/rust#51241 from today stabilizes `global_allocator` and I think all the things under `allocator_api` that we use. (Also, as part of its work, it pushes down some of liballoc's wide instability to particular modules; we might want to advocate to do more of that to stabilize the re-exported parts of liballoc to solve the previous one.)\r\n* `#![feature(const_fn)]` for `FileSystemFlags::const_empty()`. rust-lang/rust#24111 but it ... seems to have turned into developing an effect system or something?? See also bitflags/bitflags#158. Also, can't we work around this by just making it an actual constant and not a `const fn`?\r\n* `#[feature(lang_items)]` for `panic_fmt`. rust-lang/rust#44489 which seems to have a decent design and consensus but no active implementation. If we implement unwinding using `eh_personality` we'll need this more.\r\n* `#[feature(use_extern_macros)]`: I think we don't need it, #40."}}
{"actor":{"display_login":"geofft"}}