You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package stream_transformers was created as an experiment. The API has now matured and stabilized, and it might make sense to include it in package:async, rather than having two different packages.
It could be exported as a separate top-level library, to avoid the extension methods crowding the classes for users of the rest of package:async.
A strong argument in favor of making it a separate top level import is that it will be non-breaking that way. If we were to suddenly introduce these extensions from package:async/async.dart then it would introduce errors for everyone who today imports both.
There are no types introduced (publicly) by that package, so copy/paste is a valid migration path.
We would, at the same time, change package:stream_transform to export the extensions from package:async and therefore depend on a version of package:async great enough to have those.
It's still possible to get an older version of package:stream_transform and a new version of package:async, but it is possible to avoid it.
That said, I have no problem with a top-level library.
Has this idea been abandoned? I just found a useful helper in package:stream_transform by accident, I was not aware this package even exists. Yet what it does seems to align greatly with the purpose of package:async.
The package stream_transformers was created as an experiment. The API has now matured and stabilized, and it might make sense to include it in
package:async
, rather than having two different packages.It could be exported as a separate top-level library, to avoid the extension methods crowding the classes for users of the rest of
package:async
.@natebosch
The text was updated successfully, but these errors were encountered: