Export modules with RSVP to avoid destructuring

[danmcclain]

No description provided.

[rwjblue]

I like it. I'd much prefer to import named instead of importing RSVP then destructuring. I believe this also matches RAVP's normal exports.

@danmcclain - We will need to PR against Stef's pending PR in Ember itself (we need to keep these repos in sync). Would you mind doing that also?

@stefanpenner - r?

[stefanpenner]

I would prefer to wait as we decide what we want to expose. Wholesale including all the things, like cast and throw seems like a bad choice, maybe others. In addition, I am unsure about such first class promise features, such as resolve etc, which should actually by spec reside on a Promise and cannot be destructured, because they rely on this being an appropriate constructor.

[rwjblue]

@stefanpenner - Sounds good. I believe the point here was to emulate the already existing RSVP public API (taken from lib/rsvp.js).

[danmcclain]

@rwjblue Confirm, I was going for 1:1 with the current rsvp.js exports

[rwjblue]

@stefanpenner - Are those that you mentioned going to be deprecated and removed by RSVP? Either way, can you list the ones to remove from this PR so that we can at least use imports for some of the things?

[Turbo87]

closing due to inactivity