There's a blurb at the end of the Appendix document that reads:

So, if you want to start a chain by dispatching to the background, you have to use
DispatchQueue.async:

DispatchQueue.global().async(.promise) {
    return value  
}.done { value in
    //…
}

However, this function cannot return a promise because of Swift compiler ambiguity
iss

Hey,

Has any thought been given to supporting phpstan/psalm generics e.g.

class Foo
{
    /**
     * @return Promise<MyDomainThing>
     */
    public function wait(): Promise { // ... }
}

Otherewise, what's the best way to document a Promise that's compatible with SA tools?

Psalm has some stubs for Amp: https://github.com/vimeo/psalm/blob/master/src/Psalm/Internal/S

The navigation in the documentation is currently showing a horizontal scrollbar and isn't full-height.

I'm not sure if it's supposed to be full-height, but I think the horizontal scrollbar should be an easy fix by just making it slightly wider ;)

Here's a screenshot to show what I mean:
![capture](https://cloud.githubusercontent.com/assets/152227/14913804/d8c2c74c-0e05-11e6-92f5-3e2d97904e92.PNG

ZTransducer is an effectful chunk processing function, and thus forms an arrow. We should add the following combinators on it:

• zipping: (ZTransducer[A, B], ZTransducer[A, C]) => ZTransducer[A, (B, C)]
• racing: (ZTransducer[A, B], ZTransducer[A, C]) => ZTransducer[A, Either[B, C]] looks problematic to implement currently
• both: `(ZTransducer[A, C], ZTransducer[B, D]) => ZTr

https://github.com/malcommac/Hydra/blob/d12500aaf1685b338231f03cdfa49c4aa01858a3/README.md
in README.md, retry is written twice in line 20.It is good to match because the order is different from Index.

https://github.com/malcommac/Hydra/blob/d12500aaf1685b338231f03cdfa49c4aa01858a3/README.md#all-features
There is no retry in All Feature.

If people are going to use onevent props we should probably have them typed to prevent no implicit any errors. Maybe we can take the typings from Preact or something similar? My one concern is that intrinsic elements are already sorta loosely typed (data-attrs can be of type any), and I don’t really see the value of typing intr

The build section should talk about contrib. The contributing section should cover:

1. Differences between npm version and github version.
2. Process for building (or should that be in build) and running tests.
3. Contribution guidelines.

Would be nice to have TypeScript type definitions bundled in this package. The types should be strict and should be generic so it preserves the original function type.

The type defini

Add 'Best Practices For Package Developers using Futures' vignette with instructions on, for instance,

1. How to test code, e.g. run tests with plan(sequential) and plan(multisession) and don't assume that plan(multicore) is available.

2. Make sure to shut down PSOCK clusters at the end of examples and package tests, i.e. call plan(sequential) at the end (e.g. #327)

3. Avoid setti

Placeholder for retiring the dedicated sift.js library.

Description:
sift.js was originally written to provide a centralized location for hardware filtering:

• MAC Address filtering
• Raw printer filtering
• Process USB output to human readable formats

Justification
Although sift.js is still used as part of QZ Tray (since 2.1), it doesn't get enough changes to make sense a

From https://discuss.ocaml.org/t/lwt-how-to-catch-exceptions-raised-by-signal-handlers/565:

open Lwt.Infix

let () =
  Lwt_unix.on_signal
    Sys.sigint
    (fun _ ->
      failwith "Caught SIGINT")
  |> ignore;

  let p =
    Lwt.finalize
      (fun () ->
        Lwt_unix.sleep 2. >>= fun () ->
        raise Pervasives.Exit)
      (fun () -