Skip to content

Drive-by mention unsafe fn closure coercion #802

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

Merged
merged 2 commits into from
Jul 29, 2020
Merged

Drive-by mention unsafe fn closure coercion #802

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d0ab22d
Drive-by mention unsafe fn closure coercion
Apr 16, 2020
f740783
Update src/types/closure.md
nikomatsakis Jul 29, 2020
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
4 changes: 2 additions & 2 deletions src/types/closure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,8 +131,8 @@ more specific call traits:
> not how it captures them.

*Non-capturing closures* are closures that don't capture anything from their
environment. They can be coerced to function pointers (`fn`) with the matching
signature.
environment. They can be coerced to function pointers (`fn` or `unsafe fn`)
with the matching signature.

```rust
let add = |x, y| x + y;
Expand Down