Redesign DyNet API
Open
minor bug
- Dominant language
- C++
- Stars
- 3.4k
- Forks
- 701
- PR merge metrics
- No merged PRs in 30d
Description
I found the names of some APIs are confusing. For example, `sum_elems` vs `esum`. Any plan on revising them?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the definitions and call sites for `sum_elems` and `esum`, then review the surrounding DyNet API naming conventions. Done would require a concrete, agreed naming redesign and an implementation scope; the issue currently asks only whether there is a plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, machine-learning
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100