---

yaml
---
r: 13173
b: refs/heads/master
c: 3c622a5
h: refs/heads/master
i:
  13171: 2975037
v: v3

Author: lkuper

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 43eb5f0a2e9fb52e154ac9a463061bb673431f19
+refs/heads/master: 3c622a5b1278484f02d49cb37cfb7005239f30a4
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 4a81779abd786ff22d71434c6d9a5917ea4cdfff
 refs/heads/try: 2898dcc5d97da9427ac367542382b6239d9c0bbf

trunk/src/test/compile-fail/regions-fn-subtyping.rs

@@ -1,5 +1,3 @@
-// Issue #2263.
-
 // Here, `f` is a function that takes a pointer `x` and a function
 // `g`, where `g` requires its argument `y` to be in the same region
 // that `x` is in.
@@ -13,6 +11,11 @@ fn has_same_region(f: fn(x: &a.int, g: fn(y: &a.int))) {
 }
 
 fn wants_two_regions(_f: fn(x: &int, g: fn(y: &int))) {
+    // Suppose we were to write code here that passed some arbitrary
+    // &int and some arbitrary fn(&int) to whatever's passed in as _f.
+    // This would be fine as far as the type annotation on the formal
+    // parameter _f goes, but if _f were `f` we'd be in trouble since
+    // `f` can't handle those arguments.
 }
 
 fn main() {