future

I push my Futures from a ExecutorService into a hash map. Later, I may call cancel on Futures from within the hash map. Although the result is true, I later hit breakpoints within the Callable procedure, as if the Future cancel() had no effect. I think it might be a case of two different references here (even though the reference IDs are listed as the same when breakpointing), but was wondering if some experts could chime in. Here's what the code looks like: ExecutorService taskExecutor = Executors.newCachedThreadPool(); Map <String, Future<Object>> results = new HashMap <String, Future<Object

In a language like C#, giving this code (I am not using the await keyword on purpose): async Task Foo() { var task = LongRunningOperationAsync(); // Some other non-related operation AnotherOperation(); result = task.Result; } In the first line, the long operation is run in another thread, and a Task is returned (that is a future). You can then do another operation that will run in parallel of the first one, and at the end, you can wait for the operation to be finished. I think that it is also the behavior of async / await in Python, JavaScript, etc. On the other hand, in Rust, I read in the

I am a newbie to scala futures and I have a doubt regarding the return value of scala futures. So, generally syntax for a scala future is def downloadPage(url: URL) = Future[List[Int]] { } I want to know how to access the List[Int] from some other method which calls this method. In other words, val result = downloadPage("localhost") then what should be the approach to get List[Int] out of the future ? I have tried using map method but not able to do this successfully.` Alexey Romanov The case of Success(listInt) => I want to return the listInt and I am not able to figure out how to do that.

Is it possible to check if a std::future has finished or not? As far as I can tell the only way to do it would be to call wait_for with a zero duration and check if the status is ready or not, but is there a better way? You are correct, and apart from calling wait_until with a time in the past (which is equivalent) there is no better way. You could always write a little wrapper if you want a more convenient syntax: template<typename R> bool is_ready(std::future<R> const& f) { return f.wait_for(std::chrono::seconds(0)) == std::future_status::ready; } N.B. if the function is deferred this will

Is it possible to disable future date from today? Let say today is 23/10/2010, so 24/10/2010 onwards are disabled. Sorry I am very new in jQuery and JavaScript. Cyril Gupta Yes, indeed. The datepicker has the maxdate property that you can set when you initialize it. Here's the codez $("#datepicker").datepicker({ maxDate: new Date, minDate: new Date(2007, 6, 12) }); $(function() { $("#datepicker").datepicker({ maxDate: '0'}); }); JAY Code for Future Date only with disable today's date. var d = new Date(); $("#delivdate").datepicker({ showOn: "button", buttonImage: base_url+"images/cal.png",

Suppose I have several futures and need to wait until either any of them fails or all of them succeed. For example: Let there are 3 futures: f1 , f2 , f3 . If f1 succeeds and f2 fails I do not wait for f3 (and return failure to the client). If f2 fails while f1 and f3 are still running I do not wait for them (and return failure ) If f1 succeeds and then f2 succeeds I continue waiting for f3 . How would you implement it? You could use a for-comprehension as follows instead: val fut1 = Future{...} val fut2 = Future{...} val fut3 = Future{...} val aggFut = for{ f1Result <- fut1 f2Result <- fut2