[Feature] Handle batch information in dgl.reverse
Open
feature request
- Dominant language
- Python
- Stars
- 14.3k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I found some arguments in `reverse` has been renamed. Since I'm not sure whether
ignoring batch configuration of input graph `g` is intended or not, I raised this issue as a question.
I guess the `reverse` function shouldn't throw away inputs' batch statistics.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.