Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't allocate in rt::context::Context::new #7767

Closed
catamorphism opened this issue Jul 13, 2013 · 1 comment
Closed

Don't allocate in rt::context::Context::new #7767

catamorphism opened this issue Jul 13, 2013 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows I-slow Issue: Problems and improvements with respect to performance of generated code.

Comments

@catamorphism
Copy link
Contributor

FIXME says: "Putting main into a ~ so it's a thin pointer and can
// be passed to the spawn function. Another unfortunate
// allocation". Figure out how to not do this.
@emberian
Copy link
Member

FIXME still there. I don't see an obvious way to work around this. As it is it's going to be a tiny two-word allocation, and I don't think this is going to be an issue.

flip1995 pushed a commit to flip1995/rust that referenced this issue Oct 7, 2021
@bors
Auto merge of rust-lang#7770 - zvavybir:master, r=xFrednet
b9dedf3 
improved help message for `suspicious_map`

`suspicious_map`'s help message assumes that the literal behavior is never the intended one, although it's sometimes.  This PR adds a mention of `inspect`, offering a idiomatic alternative.

fixes rust-lang#7767

---

changelog: Improved help message of [`suspicious_map`].
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows I-slow Issue: Problems and improvements with respect to performance of generated code.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@catamorphism @emberian