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

When using trainAll finished function should be optional #12

Closed
manthanhd opened this issue Oct 28, 2016 · 2 comments
Closed

When using trainAll finished function should be optional #12

manthanhd opened this issue Oct 28, 2016 · 2 comments

Comments

@manthanhd
Copy link
Owner

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?

@anubhavsrivastava
Copy link

It does not make it less explicit. Calling without finishedFunc should return new Error(...) to the caller.

@manthanhd
Copy link
Owner Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants