Giter VIP home page Giter VIP logo

Comments (5)

josephearl avatar josephearl commented on August 25, 2024

I'm not sure I understand, [BFTask waitUntilFinished] waits until the current task is completed, and if it completed successfully you will be immediately able to access the result.

Continuations may run after waitUntilFinished has returned, but those are for following tasks and not the current task so I see no issue there.

from bolts-objc.

leewinder avatar leewinder commented on August 25, 2024

In this specific case, I expected the execution block to be called before [BFTask waitUntilFinished] returned which isn't the case. I expect this as I need to use the results of that block immediately after the call to [BFTask waitUntilFinished] on the same thread.

Continuations do continue for other tasks within the queue, thats fine and as expected, but this refers to the specific task being waited on.

from bolts-objc.

josephearl avatar josephearl commented on August 25, 2024

If you do something like:

BFTask *task = [client findAsync:query];
[task continueWithSuccessBlock:^id(BFTask *task) {
  NSLog(@"Continuation has run");
  return nil;
}]
[task waitUntilCompletion];

then when waitUntilCompletion returns the continuation will not have executed yet (and the message will not have been logged).

What you need is to do use the task returned from continueWithBlock:

BFTask *task = [client findAsync:query];
BFTask *continuationTask = [task continueWithSuccessBlock:^id(BFTask *task) {
  NSLog(@"Continuation has run");
  return nil;
}]
[continuationTask waitUntilCompletion];

then waitUntilCompletion will not return until the continuation has run (and message logged).

from bolts-objc.

leewinder avatar leewinder commented on August 25, 2024

Ok, thats useful to know. The behaviour of my initial structure still seems incorrect though, but maybe that's just a documentation issues.

I say that because I have the same code paths for both async and (for testing) synchronous calls with an optional call to [task waitUntilCompletion], which to me made the most sense.

But like I say, maybe it just needs to be documented.

from bolts-objc.

 avatar commented on August 25, 2024

Thanks guys!
Closing this one, as the issue seems to be resolved now.
Feel free to reopen or send a Pull Request if you think there is anything actionable here.

from bolts-objc.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.