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

One more import refactoring #203

Closed
wants to merge 1 commit into from
Closed

One more import refactoring #203

wants to merge 1 commit into from

Conversation

espindola
Copy link

I am finally happy with this structure. It is efficient (module the unnecessary copying), isolated for next stages and somewhat easy to understand.

* Create an import resolving stage. Currently this involves a copy of the ast,
  we can probably revisit this once we revisit doing full copies of the ast in
  general.

* Don't repeat work. Once we resolve a import, put it on a hash table and use
  it next time we are asked for it. This solves a O(n^2) behaviour in
  degenerated cases.

* Once import resolution is done, the target of an import is stored on the
  import itself.
@graydon
Copy link
Contributor

graydon commented Jan 19, 2011

Merged

oli-obk added a commit to oli-obk/rust that referenced this pull request Jul 19, 2017
Allow any offset on integer and ZST pointers
kazcw pushed a commit to kazcw/rust that referenced this pull request Oct 23, 2018
…ust-lang#203)

* [ci] upgrade to cupid 0.0.5

* [runtime x86] cleanup duplicated code
djtech-dev pushed a commit to djtech-dev/rust that referenced this pull request Dec 9, 2021
matthiaskrgr pushed a commit to matthiaskrgr/rust that referenced this pull request Mar 7, 2023
This pull request was closed.
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.

3 participants