Replies: 1 comment 6 replies
-
|
Can you give me a use case you want to be supported? Almost any use case I can picture can be handled by capturing a variable from the environment. |
Beta Was this translation helpful? Give feedback.
-
|
In order for this to work, func doSomething(task any) func() {
return func() {
println(task)
}
}Making |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you for your answer. var wg conc.WaitGroup
for _, task := range tasks {
wg.GoParameters(doSomething,task,1)
}
wg.Wait()Or use indefinite parameters. This way requires reflection in implementation, which is not a good way. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it's unfortunate that we can't be generic over the number of arguments. There were quite a few places where I'd really love to be able to name a type that basically means "this function returns a value and an error, or just an error". Unfortunately, that's not yet possible |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, I also understand the considerations |
Beta Was this translation helpful? Give feedback.
-
|
I think this would be possible. But if the parameters wouldn't match the function definition you would get error at runtime instead of at compilation time which is not really good experience. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
wg.Go(func() { ... })
func() does not support parameters and has limited use
Beta Was this translation helpful? Give feedback.
All reactions