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

Explain more in depth what early and late bound generic parameters are #1732

Merged
merged 4 commits into from
Jul 11, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
caps is so important
Co-authored-by: Michael Goulet <michael@errs.io>
BoxyUwU and compiler-errors authored Jul 11, 2023

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
commit 3edc31e798ef0c1892f00c11b175a32c7f9a7d69
2 changes: 1 addition & 1 deletion src/early-late-bound.md
Original file line number Diff line number Diff line change
@@ -14,7 +14,7 @@ with this topic.

## What does it mean for parameters to be early or late bound

All function definitions conceptually have a zst (this is represented by `TyKind::FnDef` in rustc).
All function definitions conceptually have a ZST (this is represented by `TyKind::FnDef` in rustc).
The only generics on this zst are the early bound parameters of the function definition. e.g.
```rust
fn foo<'a>(_: &'a u32) {}