Skip to content

Commit

Permalink
Confusing description about task queue
Browse files Browse the repository at this point in the history
Summary:
Just can't get the point. What does `the next task that might have been queued up earlier` mean? Earlier than what? `The first task`? Please correct me if I missed something.
Closes facebook#4970

Reviewed By: svcscm

Differential Revision: D2789390

Pulled By: sahrens

fb-gh-sync-id: 3078fb6cbc7940d26d2dc393ba9448f132721ea2
  • Loading branch information
sunnylqm authored and facebook-github-bot-5 committed Dec 25, 2015
1 parent e4272b4 commit a47fcd4
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions Libraries/Interaction/TaskQueue.js
Original file line number Diff line number Diff line change
Expand Up @@ -35,10 +35,9 @@ export type Task = Function | SimpleTask | PromiseTask;
* function is supplied, then the promise it returns will block execution of
* tasks already in the queue until it resolves. This can be used to make sure
* the first task is fully resolved (including asynchronous dependencies that
* also schedule more tasks via `enqueue`) before starting on the next task that
* might have been queued up earlier. The `onMoreTasks` constructor argument is
* used to inform the owner that an async task has resolved and that the queue
* should be processed again.
* also schedule more tasks via `enqueue`) before starting on the next task.
* The `onMoreTasks` constructor argument is used to inform the owner that an
* async task has resolved and that the queue should be processed again.
*
* Note: Tasks are only actually executed with explicit calls to `processNext`.
*/
Expand Down

0 comments on commit a47fcd4

Please sign in to comment.