-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
@code_llvm, @code_native, etc. macros? #5674
Comments
cc: @astrieanna |
This seems like it might be a bit brittle since the only input types that could be reasoned about by the macro are those with literal syntax that uniquely defines the types: Int, Float64 and ByteString. For most other functions I'm not sure how'd you make this work. |
You could just rewrite |
That's true: you could defer type knowledge to runtime. |
Yes, @simonster has the right idea. |
great idea |
I want |
Closed by #5832. |
Similar to the
@which
macro, could we also have thecode_...
family of functions available as macros? That would allow one to check generated code even faster:would translate to a call of:
code_llvm(Date,(Int64,Int64,Int64))
This would be a pull request, but my meta chops are probably not quite Base-worthy, after taking a look at the
@which
implementation.The text was updated successfully, but these errors were encountered: