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

Iterator.get_next() documentation improvement request #16954

Closed
jlysiak opened this issue Feb 12, 2018 · 0 comments
Closed

Iterator.get_next() documentation improvement request #16954

jlysiak opened this issue Feb 12, 2018 · 0 comments
Assignees
Labels
stat:awaiting tensorflower Status - Awaiting response from tensorflower type:docs-bug Document issues

Comments

@jlysiak
Copy link

jlysiak commented Feb 12, 2018

System information

N/A

Describe the problem

Recently I've written some code using Dataset API and I would like to request a problem with documentation (IMO). Instead of hardcoding comments here, please, move @mrry's annotation about Iterator.get_next() and GET_NEXT_CALL_WARNING_THRESHOLD into get_next() method documentation.

I don't know why I didn't get that beautiful warning on my console output but I think I'm not the first person with funny thread-bomb running and consuming system resources. :) You know about that also (see comment).
So... It would be great if you could move all critical annotation into main documentation. I'm thinking now about all ML newcomers rather than me (Yeah, I actually found solution by myself :))
That's all.

Source code / logs

N/A

@mrry mrry self-assigned this Feb 12, 2018
@mrry mrry added type:docs-bug Document issues stat:awaiting tensorflower Status - Awaiting response from tensorflower labels Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat:awaiting tensorflower Status - Awaiting response from tensorflower type:docs-bug Document issues
Projects
None yet
Development

No branches or pull requests

2 participants