Escape from Callback Hell: Callbacks are the modern goto

Re:Escape from Callback Hell: Callbacks are the modern goto by pufuwozu on Friday November 02, 2012 @02:07PM (#4733950)

There's a way without exceptions. Use an ErrorT[Promise[A]] monad. I've done this in Scala before and it is so much simpler than the JavaScript convention you pointed out.

It allows you to write code like this:

    val query = "Brian"
    val result = for {
      db <- connectToDatabase
      user <- userFromDatabase(db, query)
      friends <- friendsFromDatabase(db, user.friends)
    } yield friends

Whenever one of the functions above returns an error, the whole expression is that error. The outcome is either an error (if there was any) or the end value of Set[User]. No need to manually handle an error until you get to the end result.

[ Parent | on HN ]

Re:Escape from Callback Hell: Callbacks are the modern goto by saryant on Friday November 02, 2012 @02:58PM (#4734203)

Similar to this is the Scala fold convention.

An example from the Play! Framework for form submissions:

    def submit = Action { implicit request =>
      contactForm.bindFromRequest.fold(
        errors => BadRequest(html.contact.form(errors)),
        contact => Ok(html.contact.summary(contact))
      )
    }

[ Parent | on HN ]

Re:Escape from Callback Hell: Callbacks are the modern goto by pfraze on Friday November 02, 2012 @03:21PM (#4734292)

That's basically what the promises spec for Javascript gives you.

[ Parent | on HN ]

Re:Escape from Callback Hell: Callbacks are the modern goto by pufuwozu on Friday November 02, 2012 @05:12PM (#4734769)

Exactly. The promises spec defines the Promise monad. The problem is that JavaScript doesn't have monadic syntax, which would make the code a lot more readable.

[ Parent | on HN ]