using this as the example
const T = struct {
//....
pub fn foo(t: *T) void {
//...
}
};
you would do this
const t = T {
//...
};
std.Thread.spawn(config, T.foo, .{&t});
t.foo()
is just sugar for T.foo(&t)
regarding the compile error, prociding the source of runner
would help but my guess is:
Thread.spawn
eventualy gets to @call
which calls the function with the provided args, it expects a tuple struct, that being a struct with no field names.
I think thats the cause of your wierd error, however my tests have always gotten a clear expected tuple struct
error.
also your code shouldnt compile with {}
after spawn
, im guessing thats supposed the be a catch
block