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
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
Given a user-provided hook which yields arbitrary "compatibility information" (e.g., a list of symbols and associated types) about a project at a specific version, we could potentially build a compatibility checker which end-users could run when trying to determine whether to upgrade.
This could be used to catch SemVer violations, but it could also identify cases where breaking changes were introduced but they don't affect the dependent project in question.
Given a user-provided hook which yields arbitrary "compatibility information" (e.g., a list of symbols and associated types) about a project at a specific version, we could potentially build a compatibility checker which end-users could run when trying to determine whether to upgrade.
This could be used to catch SemVer violations, but it could also identify cases where breaking changes were introduced but they don't affect the dependent project in question.
h/t @cbarrett
The text was updated successfully, but these errors were encountered: