about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2014-01-02 02:11:48 -0800
committerbors <bors@rust-lang.org>2014-01-02 02:11:48 -0800
commitbbdf6458112f33c0c72ebdedb1f1c93bd737d3a8 (patch)
tree84e19cd00c24015b230a79d32d4a5e9df1272727
parentee634e3ac455032227f44ee7577b3d65be4acb61 (diff)
parent99dbb1d51f3f08d1cd94179687cbe69c3218ef87 (diff)
downloadrust-bbdf6458112f33c0c72ebdedb1f1c93bd737d3a8.tar.gz
rust-bbdf6458112f33c0c72ebdedb1f1c93bd737d3a8.zip
auto merge of #11268 : lkuper/rust/trans-comment, r=pcwalton
-rw-r--r--src/librustc/middle/trans/base.rs2
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.