Skip to content

Tracking issue for type checking refactor #26597

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
5 of 6 tasks
jroesch opened this issue Jun 26, 2015 · 5 comments
Closed
5 of 6 tasks

Tracking issue for type checking refactor #26597

jroesch opened this issue Jun 26, 2015 · 5 comments

Comments

@jroesch
Copy link
Member

jroesch commented Jun 26, 2015

This a placeholder issue to contain our conversation and set of pull requests around the type checking refactor. The goal of the work is to unify our type checking contexts into a single piece of state. We hope to eventually have a single context instead of the fractured situation we currently have.

@eddyb
Copy link
Member

eddyb commented Jun 26, 2015

cc @rust-lang/compiler

@steveklabnik
Copy link
Member

@jroesch bump! You only have one box not checked here, can this be closed?

@Mark-Simulacrum
Copy link
Member

I'd be happy to do the work renaming things if given a list (or even an approximate list, general idea).

@eddyb
Copy link
Member

eddyb commented Jan 4, 2017

I'm not even sure what we should do now, it's likely time for a cache-reuse-targetted redesign.

@nikomatsakis
Copy link
Contributor

I think we can close this issue, since I think this path of changes is dead. I have some new plans I hope to write up in the next few days (or weeks...) though.

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

No branches or pull requests

5 participants