-
Notifications
You must be signed in to change notification settings - Fork 165
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
generic interface cannot be used as a generic argument #3804
Labels
goal:client exploration
Speculative work for a potential use case.
inactive:wontfix
out of scope, or not desired
Milestone
Comments
This is due to some fundamental limitation we have in our IR. Supporting this is likely something we cannot afford in the short term. Let's try:
If this doesn't work, we may be able to fix it. |
Oh. I got it wrong. |
This issue was closed as WNF due to the low bang for the buck. |
csyonghe
added a commit
to csyonghe/slang
that referenced
this issue
Aug 20, 2024
csyonghe
added a commit
that referenced
this issue
Aug 21, 2024
* Support dependent generic constraints. * Fix warning. * Update comment. * Fix. * Add a test case to verify fix of #3804. * Address review.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
goal:client exploration
Speculative work for a potential use case.
inactive:wontfix
out of scope, or not desired
When an interface uses "__generic", the interface cannot be used as a part of the __generic argument.
It is easier to explain the problem with an example.
The following code gives us a compile error,
The error message is following,
The following alternative approach didn't work either,
The error message is identical to the first example.
The text was updated successfully, but these errors were encountered: