Activity

1. cramertj commented on Sep 20, 2018

   

   cramertj

   on Sep 20, 2018

   Member

   More actions

   This was discussed on another thread (trying to track it down, but a quick look didn't turn it up) and the plan was to allow adding alloc to the extern list by providing a flag in Cargo.toml that made cargo pass a --extern alloc (with no value for x in --extern alloc=<x>). This would cause the named crates to be included in the extern prelude (if found in the link path).
2. Nemo157 commented on Sep 21, 2018

   

   Nemo157

   on Sep 21, 2018

   Last edited by Nemo157

   Contributor

   More actions

   I believe the change @cramertj mentions is slated to be a post-2018 feature (since there are still design considerations for the cargo side of it). Until then use of extern crate {alloc,test,proc_macro}; are all still needed (only the last is possible on stable, the first two are unstable crates).

   Edit: see #54116 (comment) and I think
   #53130 (comment) is the most fleshed out comment on how this may look in the future.
3. estebank

   added

   T-langRelevant to the language teamRelevant to the language team

   T-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]

   on Sep 21, 2018
4. petrochenkov commented on Dec 1, 2018

   

   petrochenkov

   on Dec 1, 2018

   Contributor

   More actions

   alloc still requires using extern crate alloc as now documented in https://rust-lang-nursery.github.io/edition-guide/rust-2018/module-system/path-clarity.html
5. petrochenkov

   closed this as completedon Dec 1, 2018