Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(564)

Unified Diff: src/parser.cc

Issue 1022413003: Fix unintentional typo in Parser::ParseLazy() comments (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master
Patch Set: Created 5 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: src/parser.cc
diff --git a/src/parser.cc b/src/parser.cc
index f24f7107d8fd444235349dcc2601166dcc8ebbdc..be8c3f30de25af5f19fe5285a8411083486f9390 100644
--- a/src/parser.cc
+++ b/src/parser.cc
@@ -1150,7 +1150,7 @@ FunctionLiteral* Parser::ParseLazy(Isolate* isolate, ParseInfo* info,
// stack overflow, at which point the partially parsed arrow
// function concise body happens to be a valid expression. This
// is a problem only for arrow functions with single statement
- // bodies, since there is no end token suck as "}" for normal
+ // bodies, since there is no end token such as "}" for normal
// functions.
if (scanner()->location().end_pos == shared_info->end_position()) {
// The pre-parser saw an arrow function here, so the full parser
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698