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.

Sign up for GitHub

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

Jump to bottom

include universe quantifiers in the Quantified<T> type #1

Closed
nikomatsakis opened this issue Jan 6, 2017 · 0 comments
Closed

include universe quantifiers in the Quantified<T> type #1

nikomatsakis opened this issue Jan 6, 2017 · 0 comments

Comments

@nikomatsakis
Copy link
Contributor

No description provided.

nikomatsakis referenced this issue in nikomatsakis/chalk-ndm Dec 16, 2019
@nikomatsakis
extract placeholders from a type-name into their own variant
f6546e5 
Motivation #1: We want type-names to be opaquely defined by the type
family. The fact that we had to fold `ApplicationTy` into `Ty` should
have been a sign that something should change.

Motivation rust-lang#2: Although this commit does get that far, we want to
treat associated type placeholders akin to ordinary ones.
nikomatsakis referenced this issue in nikomatsakis/chalk-ndm Dec 18, 2019
@nikomatsakis
extract placeholders from a type-name into their own variant
4667bac 
Motivation #1: We want type-names to be opaquely defined by the type
family. The fact that we had to fold `ApplicationTy` into `Ty` should
have been a sign that something should change.

Motivation rust-lang#2: Although this commit does get that far, we want to
treat associated type placeholders akin to ordinary ones.
bors pushed a commit that referenced this issue Nov 15, 2020
@drtychai
Hyperlink protocol changed: HTTP -> HTTPS (#1)
b672c7a
bors added a commit that referenced this issue Nov 15, 2020
@bors
Auto merge of #652 - drtychai:master, r=jackh726
e9c82ba 
Hyperlink protocol changed: HTTP -> HTTPS (#1)

Just as the title says; if the domain supported HTTPS, then the protocol was appropriately changed.

The following ~two~ three sites were the only ones without TLS support configured:
- `wambook.sourceforge.net`
- `minikanren.org`
- `blog.ezyang.com`

FWIW, I went through and clicked at least one link for each unique FQDN.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nikomatsakis