Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nit: misplaced comma #221

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Nit: misplaced comma #221

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion web/finagle.textile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ In practice, you won't write code that sends a request and then calls <code>Awai

If you've used other asynchronous APIs, you perhaps cringed when you saw the word "callbacks" just now. You might associate them with illegible code flows, functions hiding far from where they're invoked. But Futures can take advantage of Scala's first-class functions to present a more-readable code flow. You can define a simpler handler function in the place where it's invoked.

For example to, write code that dispatches a request and then "handles" the response, you can keep the code together:
For example, to write code that dispatches a request and then "handles" the response, you can keep the code together:

<pre>
val future = dispatch(req) // returns immediately, but future is "empty"
Expand Down