Skip to content

Extract stack management code from rust_task #2044

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.

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

Closed
brson opened this issue Mar 21, 2012 · 1 comment
Closed

Extract stack management code from rust_task #2044

brson opened this issue Mar 21, 2012 · 1 comment
Assignees
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Mar 21, 2012

A large portion of rust_task is now dedicated to fiddling with stacks. This code should probably be extracted into another class.

@graydon
Copy link
Contributor

graydon commented Mar 12, 2013

I think this is redundant with #5022 so closing

@graydon graydon closed this as completed Mar 12, 2013
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
…e links to the corresponding md source files. (rust-lang#2044)

Use relative links to the corresponding md source files; this helps local browsing of generated docs.
bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 2, 2025
…e links to the corresponding md source files. (rust-lang#2044)

Use relative links to the corresponding md source files; this helps local browsing of generated docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

2 participants