expede
commented
1 year ago The good news is that this does separate cleanly. The bad news is that I don't know how useful it is to do so. IPLD Schema isn't expressive enough to say "without promises" for example, so a distinctin like that all has to get described in prose anyways. As noted earlier, most projects so far have found having the option of promises useful, even if it's not immedietly obvious.
Good to know that this is an option, but there's no forcing function on this right now.
This is an EXPERIMENTAL branch forked from the
fix-typosbranch (#11).In general, we find that people actually do want promises after thinking about it, but separating them out may provide an easier onramp. It also may help clarify a resolved TaskID versus something more akin to a ClosureID.
UPDATE: To wit, we had a dinner with a partner team last week who didn't think they needed promises. Turns out that they do need them, so keeping with the trend of people often actually needing promises, breaking this out may not actually make sense.