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.

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

rustc: Crawl static initializers for reachability #13906

Merged
merged 1 commit into from
May 4, 2014

Conversation

alexcrichton
Copy link
Member

This ensures that private functions exported through static initializers will
actually end up being public in the object file (so other objects can continue
to reference the function).

Closes #13620

This ensures that private functions exported through static initializers will
actually end up being public in the object file (so other objects can continue
to reference the function).

Closes rust-lang#13620
bors added a commit that referenced this pull request May 3, 2014
This ensures that private functions exported through static initializers will
actually end up being public in the object file (so other objects can continue
to reference the function).

Closes #13620
@bors bors closed this May 4, 2014
@bors bors merged commit 18ac265 into rust-lang:master May 4, 2014
@alexcrichton alexcrichton deleted the issue-13620 branch May 4, 2014 18:52
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jan 9, 2025
…ust-lang#13906)

Proper parentheses need to be added to some expressions in receiver
position.

Fix rust-lang#13902

changelog: [`redundant_pattern_matching`]: use proper parentheses when
suggesting replacing `matches!(…, None)` by `.is_none()`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Static items can result in references to unexported symbols
3 participants