-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
universes refactor 3 #55305
universes refactor 3 #55305
Commits on Oct 27, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 018c515 - Browse repository at this point
Copy the full SHA 018c515View commit details -
Configuration menu - View commit details
-
Copy full SHA for 784746f - Browse repository at this point
Copy the full SHA 784746fView commit details -
allow canonicalized regions to carry universe and track max-universe
But.. we don't really use it for anything right now.
Configuration menu - View commit details
-
Copy full SHA for 3ef27d8 - Browse repository at this point
Copy the full SHA 3ef27d8View commit details -
extend query response to potentially contain fresh universes
The idea here is that an incoming query may refer to some universes, and they query response may contain fresh universes that go beyond those. When we instantiate the query response in the caller's scope, therefore, we map those new universes into fresh universes for the caller.
Configuration menu - View commit details
-
Copy full SHA for 7f9ab60 - Browse repository at this point
Copy the full SHA 7f9ab60View commit details -
Configuration menu - View commit details
-
Copy full SHA for 80d9f8b - Browse repository at this point
Copy the full SHA 80d9f8bView commit details -
distinguish user-type annotations from other annotations
In particular, we don't want to preserve the universes for the `'_` variables that appear in there. And we don't expect to find any placeholders, which justifies this as harmless. (In particular, if you have a query like `Foo(!1, !2, ?3)`, then you care about the universe of `?3`, since it may control whether `?3 = !1` and `?3 = !2` is a valid answer. But without any placeholders, we don't really care: any placeholders that would appear in the output must therefore come from some fresh universe anyway.)
Configuration menu - View commit details
-
Copy full SHA for bf51840 - Browse repository at this point
Copy the full SHA bf51840View commit details -
apply minimum bounds when checking closure signature
Required for test expect-fn-supply-fn.rs to pass; otherwise we have unconstrained inference variables that get inferred to `'empty`.
Configuration menu - View commit details
-
Copy full SHA for d4e4e37 - Browse repository at this point
Copy the full SHA d4e4e37View commit details -
Configuration menu - View commit details
-
Copy full SHA for b24b887 - Browse repository at this point
Copy the full SHA b24b887View commit details -
Configuration menu - View commit details
-
Copy full SHA for a1be20c - Browse repository at this point
Copy the full SHA a1be20cView commit details
Commits on Oct 31, 2018
-
fix bug in NLL error reporting
Account for incompatible universes and higher-ranked subtyping.
Configuration menu - View commit details
-
Copy full SHA for 740117f - Browse repository at this point
Copy the full SHA 740117fView commit details -
Configuration menu - View commit details
-
Copy full SHA for c244fd7 - Browse repository at this point
Copy the full SHA c244fd7View commit details