-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Rewrite resolve #13449
Comments
cc me |
Additional tasks: clarify our rules (I have a plan, will post RFC soon) |
Not 1.0; marking P-high. |
cc #5765 |
Again \o/ |
I'm working on this - just by reading and working on the code myself I have a pretty good idea of some major restructurings that ought to be done, but I'd greatly appreciate information about what others think needs to be fixed. |
More specifically, I plan to separate the passes of resolve to break the implicit data dependencies, make |
triage: P-low |
Triage: what would make this ticket actionable? the last meaningful comment was 18 months ago. |
Since the last meaningful comment has been made in October 2014, resolve has been split out into its own crate and touched by almost one thousand commits, including 87 that include the word "refactor" in their one-line commit message. Whatever code this issue originally referred to, odds are it's completely unrecognizable/gone by now. |
@petrochenkov and @jseyfried (and other people I forget now, sorry!) have put a lot of work into it |
I've heard from multiple people that resolve needs a complete rewrite. Nominating.
cc #11870 #3352
The text was updated successfully, but these errors were encountered: