Suggest extern crate alloc when using undeclared module alloc#90507
Suggest extern crate alloc when using undeclared module alloc#90507bors merged 2 commits intorust-lang:masterfrom
extern crate alloc when using undeclared module alloc#90507Conversation
|
r? @jackh726 (rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
|
This seems reasonable and helpful, as an improvement to the error message. 👍 for making this change. But also, I wonder if we could arrange to always make |
|
@bors r+ rollup I think making alloc available like std or core would be nice, but should be a followup. |
|
📌 Commit 6c1e194 has been approved by |
bors
added
S-waiting-on-bors
Rollup of 9 pull requests Successful merges: - rust-lang#90507 (Suggest `extern crate alloc` when using undeclared module `alloc`) - rust-lang#90530 (Simplify js tester a bit) - rust-lang#90533 (Add note about x86 instruction prefixes in asm! to unstable book) - rust-lang#90537 (Update aarch64 `target_feature` list for LLVM 12.) - rust-lang#90544 (Demote metadata load warning to "info".) - rust-lang#90554 (Clean up some `-Z unstable-options` in tests.) - rust-lang#90556 (Add more text and examples to `carrying_{add|mul}`) - rust-lang#90563 (rustbot allow labels) - rust-lang#90571 (Fix missing bottom border for headings in sidebar) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
|
@jackh726 |
|
@TaKO8Ki I'm not sure :) |
|
Pulling in |
|
In no_std, yes. But when std is available, alloc should be, probably. |
7 participants
closes #90136