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

Adjust the error messages to match the pattern "expected foo, found bar" #8413

Closed
wants to merge 19 commits into from
Closed

Adjust the error messages to match the pattern "expected foo, found bar" #8413

wants to merge 19 commits into from

Conversation

kud1ing
Copy link

@kud1ing kud1ing commented Aug 9, 2013

... as suggested by the coding style guide.

This is a clean retry of PR #8314 which i screwed up in rebase-land.

@pcwalton: r?

alexcrichton and others added 16 commits August 11, 2013 00:29
Mostly I did simple transformations from imperative style loops to
more functional iterator based transformations.
…lock for O(n) time, cf #3100, and optimize out several unneeded clone()s.
Since the new runtime landed, the *-nopt builders have increased cycle time by roughly an hour. I have a feeling that this is because the entire runtime is in rust and it's not being optimized at all. In that past with an optimized C++ runtime it looks like things ran faster.

This adds the ability to disable optimizations in tests only, not for the entire compiler. This means that the entire compiler and associated libraries will be built with optimizations, but the tests themselves would be built and run without optimizations.

This isn't quite as good of a guarantee as disabling optimizations everywhere, but hopefully it'll improve cycle time for the *-nopt builds to move the queue along faster.
I did this once but acciddentally undid it in a later patch.
Mostly I did simple transformations from imperative style loops to
more functional iterator based transformations.
Each commit is pretty much what it says on the tin. r anybody.
@kud1ing
Copy link
Author

kud1ing commented Aug 13, 2013

I don't know whether i do the rebasing correctly. The diff is getting less readable each time, since it accumulates other commits.

@kud1ing
Copy link
Author

kud1ing commented Aug 13, 2013

The tests do not pass due to the other commits. I really have no idea how to get this through.

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.

6 participants