Skip to content

Defailbloat fail!(&'static str) #17602

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

Merged
merged 1 commit into from
Sep 29, 2014
Merged

Conversation

Tobba
Copy link
Contributor

@Tobba Tobba commented Sep 28, 2014

rustc.rlib before: 77429264
rustc.rlib after: 76977406

This bloats Option::expects a bit, but it doesn't seem to be a problem.

This makes fail!(msg) assume that msg is a &'static str, change instances where this is not the case to fail!("{}", msg)

Closes #15792

[breaking-change]

@huonw
Copy link
Member

huonw commented Sep 28, 2014

I don't understand how this bootstraps, since fail!() is used to "throw" arbitrary objects, e.g.

fail!(FatalError);

@Tobba
Copy link
Contributor Author

Tobba commented Sep 28, 2014

In std failure is handled differently than in core, for some reason

alexcrichton added a commit to alexcrichton/rust that referenced this pull request Sep 29, 2014
@bors bors merged commit 3b9732e into rust-lang:master Sep 29, 2014
lnicola pushed a commit to lnicola/rust that referenced this pull request Jul 28, 2024
fix: handle synonymous imports with different renaming in 'merge imports'

fix rust-lang#17602
RalfJung pushed a commit to RalfJung/rust that referenced this pull request Aug 1, 2024
fix: handle synonymous imports with different renaming in 'merge imports'

fix rust-lang#17602
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.

Reduce the number of arguments to fail/fail_bounds_check/begin_unwind
4 participants