Skip to content
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

std/tasks: callback cannot be nil #17718

Merged
merged 1 commit into from
Apr 14, 2021
Merged

std/tasks: callback cannot be nil #17718

merged 1 commit into from
Apr 14, 2021

Conversation

ringabout
Copy link
Member

@ringabout ringabout commented Apr 14, 2021

Task.callback cannot be nil, we need to raise it at debug and release modes

Situations:

  • if users create a Task object without using toTask and invoke the Task
  • if users already move the Task and invoke the original Task

`Task.callback` cannot be nil, we need to raise it at debug and release mode

Situations:
- if users create a Task object without using `toTask` and invoke the Task
- if users already move the Task and invoke the Task
@Araq Araq merged commit 44657b7 into devel Apr 14, 2021
@Araq Araq deleted the xflywind-patch-2 branch April 14, 2021 17:14
@dom96 dom96 changed the title callback cannot be nil std/tasks: callback cannot be nil Apr 14, 2021
@dom96
Copy link
Contributor

dom96 commented Apr 14, 2021

Suggestion: more details in commit/PR titles :)

PMunch pushed a commit to PMunch/Nim that referenced this pull request Mar 28, 2022
`Task.callback` cannot be nil, we need to raise it at debug and release mode

Situations:
- if users create a Task object without using `toTask` and invoke the Task
- if users already move the Task and invoke the Task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants