We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm wondering why the consumer in https://github.com/vmihailenco/taskq/blob/v3/memqueue/queue.go.NewQueue() is started before returning the queue. Doesn't this go against the current design of other queues? Perhaps there is a reason why?
func NewQueue(opt *taskq.QueueOptions) *Queue { opt.Init() q := &Queue{ opt: opt, } q.consumer = taskq.NewConsumer(q) if err := q.consumer.Start(context.Background()); err != nil { panic(err) } return q }
`
The text was updated successfully, but these errors were encountered:
It is weird indeed, particularly when a Start method exists and it is exposed through the API. I realized I am calling it (twice).
Sorry, something went wrong.
No branches or pull requests
I'm wondering why the consumer in https://github.com/vmihailenco/taskq/blob/v3/memqueue/queue.go.NewQueue() is started before returning the queue. Doesn't this go against the current design of other queues? Perhaps there is a reason why?
`
The text was updated successfully, but these errors were encountered: