about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-03-31 19:33:40 -0700
committerbors <bors@rust-lang.org>2013-03-31 19:33:40 -0700
commitbe792589d0925f8f77c3b5f0fc91e1d2f7a5dfb6 (patch)
tree73d6abf922f23bdaab3d92c7469efff301e0f561
parent686f448b0ccacf66eb48d1f15fb9d51b4f9678e6 (diff)
parentd617030d635c0d93fb969d76a622774133f61f7a (diff)
downloadrust-be792589d0925f8f77c3b5f0fc91e1d2f7a5dfb6.tar.gz
rust-be792589d0925f8f77c3b5f0fc91e1d2f7a5dfb6.zip
auto merge of #5651 : luqmana/rust/incoming, r=thestinger
Change fn() -> &fn().
-rw-r--r--doc/tutorial.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tutorial.md b/doc/tutorial.md
index 9344c43ba10..874383097db 100644
--- a/doc/tutorial.md
+++ b/doc/tutorial.md
@@ -1539,9 +1539,9 @@ for spawning [tasks][tasks].
 
 Rust closures have a convenient subtyping property: you can pass any kind of
 closure (as long as the arguments and return types match) to functions
-that expect a `fn()`. Thus, when writing a higher-order function that
+that expect a `&fn()`. Thus, when writing a higher-order function that
 only calls its function argument, and does nothing else with it, you
-should almost always declare the type of that argument as `fn()`. That way,
+should almost always declare the type of that argument as `&fn()`. That way,
 callers may pass any kind of closure.
 
 ~~~~