`Thread.Pool.spawn` doesn't allow functions with same signatures as `Thread.spawn` does

[pedramcode]

Zig Version

0.12.0-dev.2543+9eda6ccef

Steps to Reproduce and Observed Behavior

/home/ABC/.zig/lib/std/Thread/Pool.zig:93:13: error: error is ignored
            @call(.auto, func, closure.arguments);
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/ABC/.zig/lib/std/Thread/Pool.zig:93:13: note: consider using 'try', 'catch', or 'if'

Expected Behavior

Not throwing that error.

[Vexu]

spawn should use RunProto instead of anytype since function body values implicitly cast to function pointers.

[nektro]

imo not a bug. it doesn't make sense for a thread function to be errorable. the user is welcome to ignore it or handle it but its not the same as main where its obvious to print a stack trace to stdio.

[Vexu]

Either way they should behave the same.

[Vexu]

Why did you close this?