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
Clash doesn't respect NOINLINE
on polyvariadic functions with "extra" arguments
#2502
Labels
Comments
Easy when you know where to look:
This doesn’t deal well with the case where the argument we specialize on lacks a NOINLINE spec; in two ways:
|
martijnbastiaan
added a commit
that referenced
this issue
Jun 17, 2023
martijnbastiaan
added a commit
that referenced
this issue
Jun 17, 2023
martijnbastiaan
added a commit
that referenced
this issue
Jun 17, 2023
4 tasks
martijnbastiaan
added a commit
that referenced
this issue
Jun 17, 2023
martijnbastiaan
added a commit
that referenced
this issue
Jun 17, 2023
christiaanb
pushed a commit
that referenced
this issue
Jun 27, 2023
NadiaYvette
pushed a commit
to NadiaYvette/clash-compiler
that referenced
this issue
Jul 30, 2023
We've released v1.8.0, which includes a fix for this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just going by the title I'm tempted to mark this as
easy
;-).Reproducer
Gives:
bbWrapper
did not get its own file.DebugApplied
log.Removing the "extra" argument
Gives:
bbWrapper
did get its own file.DebugApplied
log.Removing the polyvariadic aspect
Gives:
bbWrapper
did get its own file.DebugApplied
log.The text was updated successfully, but these errors were encountered: