Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check type hole bounds during extraction #15

Open
LPTK opened this issue Aug 11, 2017 · 0 comments
Open

Check type hole bounds during extraction #15

LPTK opened this issue Aug 11, 2017 · 0 comments

Comments

@LPTK
Copy link
Member

LPTK commented Aug 11, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant