No bug - Fix typo in MissingScopeKey comment. No review.
authorShu-yu Guo <shu@rfrn.org>
Tue, 24 Mar 2015 18:49:16 -0700
changeset 264323 bb0db528a2c4fb1d155ea108d30870bba86263c2
parent 264322 b1d39f9d8c13d9817428e8c133b81fbd338558dd
child 264324 3779bb7888d30232e88dc0d71afa6061ba1be85b
push id4718
push userraliiev@mozilla.com
push dateMon, 11 May 2015 18:39:53 +0000
treeherdermozilla-beta@c20c4ef55f08 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
milestone39.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
No bug - Fix typo in MissingScopeKey comment. No review.
js/src/vm/ScopeObject.h
--- a/js/src/vm/ScopeObject.h
+++ b/js/src/vm/ScopeObject.h
@@ -773,17 +773,17 @@ class ScopeIter
 };
 
 // The key in MissingScopeMap. For live frames, maps live frames to their
 // synthesized scopes. For completely optimized-out scopes, maps the static
 // scope objects to their synthesized scopes. The scopes we synthesize for
 // static scope objects are read-only, and we never use their parent links, so
 // they don't need to be distinct.
 //
-// That is, completely optimized out scopes have can't be distinguished by
+// That is, completely optimized out scopes can't be distinguished by
 // frame. Note that even if the frame corresponding to the static scope is
 // live on the stack, it is unsound to synthesize a scope from that live
 // frame. In other words, the provenance of the scope chain is from allocated
 // closures (i.e., allocation sites) and is irrecoverable from simple stack
 // inspection (i.e., call sites).
 class MissingScopeKey
 {
     friend class LiveScopeVal;