Support comparing libraries/packages for type compatibility #38
Labels
closed-not-planned
Closed as we don't intend to take action on the reported issue
P3
A lower priority bug or feature request
type-enhancement
A request for a change that isn't a bug
<img src="https://avatars.githubusercontent.com/u/46275?v=3" align="left" width="96" height="96"hspace="10"> Issue by munificent
Originally opened as dart-lang/sdk#2828
One planned feature of pub is the ability to have it select an appropriate configuration-specific package based on the environment the app is running in. For example, there may be a single "unittest" package that has implementations for running on the standalone VM (just printing to stdout) and the browser (generating HTML).
For this to make sense, every implementation must expose the same (or a compatible) API. Since libraries aren't first class, the current plan is to basically duck type it: it's up to the package designer to ensure all of the implementations match.
It would be very handy if pub had a feature that would let you compare two libraries/packages and would determine if their public APIs are compatible with each other. This could also be useful for upgrading a package so you can see which API changes are breaking.
The text was updated successfully, but these errors were encountered: