diff options
| author | Lindsey Kuper <lindsey@composition.al> | 2014-01-01 23:00:06 -0500 |
|---|---|---|
| committer | Lindsey Kuper <lindsey@composition.al> | 2014-01-01 23:02:02 -0500 |
| commit | 99dbb1d51f3f08d1cd94179687cbe69c3218ef87 (patch) | |
| tree | d505d7beefdd280d09c918bc1d433be3a9b1d0d9 | |
| parent | 647525545b53c8ac4900a791f3b2fb2b894a4336 (diff) | |
| download | rust-99dbb1d51f3f08d1cd94179687cbe69c3218ef87.tar.gz rust-99dbb1d51f3f08d1cd94179687cbe69c3218ef87.zip | |
Fix comment that's been wrong since ancient times (thanks, @jvns).
| -rw-r--r-- | src/librustc/middle/trans/base.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/librustc/middle/trans/base.rs b/src/librustc/middle/trans/base.rs index 4f075c79dc8..ad953440316 100644 --- a/src/librustc/middle/trans/base.rs +++ b/src/librustc/middle/trans/base.rs @@ -20,7 +20,7 @@ // * There's no way to find out the ty::t type of a ValueRef. Doing so // would be "trying to get the eggs out of an omelette" (credit: // pcwalton). You can, instead, find out its TypeRef by calling val_ty, -// but many TypeRefs correspond to one ty::t; for instance, tup(int, int, +// but one TypeRef corresponds to many `ty::t`s; for instance, tup(int, int, // int) and rec(x=int, y=int, z=int) will have the same TypeRef. |
