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 ability to add bounds on type holes was added to accommodate patterns where these bounds are required (https://github.com/epfldata/sc/commit/9ed047c7a28eaabdd7433161fc931419b78772d3), but the bounds are not yet checked during extraction.
For example, the following matches: ir"List(0)".erase match { case ir"$ls:List[$t where (t <:< String)]" => t }.
In order for type hole bounds to be checked, we need to add bound parameters to the typeHole function of QuasiBase.
The text was updated successfully, but these errors were encountered:
The ability to add bounds on type holes was added to accommodate patterns where these bounds are required (https://github.com/epfldata/sc/commit/9ed047c7a28eaabdd7433161fc931419b78772d3), but the bounds are not yet checked during extraction.
For example, the following matches:
ir"List(0)".erase match { case ir"$ls:List[$t where (t <:< String)]" => t }
.In order for type hole bounds to be checked, we need to add bound parameters to the
typeHole
function ofQuasiBase
.The text was updated successfully, but these errors were encountered: