> > > What about using a symbol for the `then` protocol? Libraries can be > upgraded to use the symbol as an alias for `then`. It set up a dependency > on ES6, of course... > > And it doesn't address the compatibility problem people want to address. > It still does I think. It's cheap for a library to add a symbol-named alias for `then`. But it's expensive for a library's clients to replace all usage sites with a different API. Even though `then` is standard, the other parts are not. - Q.defer - new jQuery.Deferred - new Future - ...etc { Kevin }Received on Monday, 22 April 2013 13:07:44 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:12 UTC