Is there a documentation, and a description of goals and current limitations compared to the python API?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 928
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
i am very interested in java bindings for tf, but i am unable to find an online documentation or a detailed description of goals and limitations.
I am particularly interested in knowing how the graph vs. eager mode execution models would be handled in java, and how graphs are constructed (i'm wondering what the equivalent, if there even is a necessity for it, to the @tf.function decorator would be that we have in the python API).
Could you describe the main differences and current limitations compared to the python API?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by reviewing the Java bindings' graph and eager execution APIs and comparing them with the Python API. Document the project's goals, current limitations, graph-construction model, and whether Java has an equivalent to Python's @tf.function decorator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100