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
Finished function should be optional. Sometimes, you don't care about when the training will finish.
What are the usability implications of this? Does making it optional make it less explicit and hence loosely typed?
The text was updated successfully, but these errors were encountered:
It does not make it less explicit. Calling without finishedFunc should return new Error(...) to the caller.
Sorry, something went wrong.
@anubhavsrivastava Yeah that's what I'm debating here. Should it really throw the error or should it just ignore the callback completely?
I find the idea of making callbacks optional similar to how most programming languages make the capturing of return value optional.
trainAll
manthanhd
No branches or pull requests
Finished function should be optional. Sometimes, you don't care about when the training will finish.
What are the usability implications of this? Does making it optional make it less explicit and hence loosely typed?
The text was updated successfully, but these errors were encountered: