-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
macro threadcall does not accept Ref
arguments
#30864
Comments
|
I didn't know
I would argue that |
I am having a similar problem with my code.
I get the following error
|
|
@StefanKarpinski How would you recommend I implement the above code in V1.3? Thanks! |
Once some version of #32600 is merged, you would use that macro. I would rewrite your code to show this but I'm a little confused about why you're using both |
I think I misunderstood how @threadcall works.
and on my laptop I saw a O(n^1/2) improvment with number of threads, but on my desktop I saw a decrease in performance with adding cores.
My laptop has the same Julia version and runs on windows. |
Help with performance is more appropriate for discourse. |
Closing, as I understand the new thread api will replace threadcall. |
@StefanKarpinski , sorry about bringing this up again, I just would like to make a quick check on this, given that 1.4 is out and the Threading funcionality is more mature. Is it still true that threadcall is an "old" thing and we should use replace it with the new Threading API? What makes me think about using threadcall is that there's no setup for the user since Julia starts with 4 libuv threads (based on the docs), but 1 julia thread unless the user specifies a |
While working on a driver for Oracle, I experimented with macro
threadcall
on this function.All
Ref
arguments are outputs of the C API.When I run this function, I get an error:
After digging into the code, I found that the problem is the
Ref
type:The text was updated successfully, but these errors were encountered: