Skip to content

Remove ret_style #4382

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
wants to merge 148 commits into from
Closed

Conversation

nikomatsakis
Copy link
Contributor

I encountered issue #3681 on my branch improving fn inference. Here is a fix.

r? @catamorphism

erickt and others added 30 commits December 20, 2012 21:16
This switches over to using structs and send_maps for
query string parsing.
For example, in let x: char = 42; This was an ICE and is now a
proper type error, as per rust-lang#3477
update after/syntax/rust.vim for removal of <-
bump 0.5 => 0.6, redirect some URLs in docs.
update mandelbrot to pipes, a few other updates
Fix a bug in Result::unwrap_err (and minor cleanup)
Convert core::io to use explicit self (for issue rust-lang#4118 and issue rust-lang#2004)
Mark some more core and std functions as pure
...as far as I know, anyway, so I xfailed this tutorial test.
Before, the type was just the enum type itself, which caused an
assertion failure in iter_variant in trans::base.

r=brson

Closes rust-lang#4229
catamorphism and others added 28 commits January 7, 2013 13:40
Trivial cleanup: use enum_is_univariant; no functional change intended.
~20% perf win for trans on -O0, with other minor improvements across the board.
No effect on -O2.
… ty_err

In general it would be good to suppress any messages involving types that
have ty_err as a sub-component, but this works for now.
This reverts commit d771830.
That is, treat `self` as if it has dynamic scope. This seems to
be harmless, and prevents an ICE as per rust-lang#3563
bors pushed a commit to rust-lang-ci/rust that referenced this pull request May 15, 2021
This commit partially reverts rust-lang#3934, opting to create a span that covers
the entire body of a closure when formatting a closure body with a
block-formatting strategy, rather than having the block-formatting code
determine if the visitor pointer should be rewound. The problem with
rewinding the visitor pointer is it may be incorrect for other (i.e.
non-artificial) AST nodes, as in the case of rust-lang#4382.

Closes rust-lang#4382
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.