[Doc] floating-point conversion functions are not included in the documentation
See original GitHub issue📚 Documentation
Functions in dgl.transforms.functional
are not included in the doc. Besides, floating-point conversion functions are not included in __all__
and thus cannot be correctly imported.
https://github.com/dmlc/dgl/blob/eabcc58e41c0b94316f60ea74ba8bc5a7b0e2096/python/dgl/transforms/functional.py#L47
Issue Analytics
- State:
- Created a year ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Type Conversion Functions - Visual Basic - Microsoft Learn
These functions are compiled inline, meaning the conversion code is part of the code that evaluates the expression. Sometimes there is no call ......
Read more >15. Floating Point Arithmetic: Issues and Limitations — Python ...
Floating -point numbers are represented in computer hardware as base 2 (binary) fractions. For example, the decimal fraction 0.125 has value 1/10 +...
Read more >What Every Computer Scientist Should Know About Floating ...
There are two reasons why a real number might not be exactly representable as a floating-point number. The most common situation is illustrated...
Read more >FloatingPoint | Apple Developer Documentation
The FloatingPoint protocol declares common arithmetic operations, so you can write functions and algorithms that work on any floating-point type.
Read more >1.11. Type Casting Intrinsics - NVIDIA Documentation Center
This section describes type casting intrinsic functions that are only supported in device code. To use these functions you do not need to ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
PR #4123 updates the list in dgl.rst to have the 18 functions from dgl.transforms.functional
__all__
that were missing before, and then sorts them all alphabetically, (in a separate commit so that it’s easy to not sort if people don’t want it sorted).Thanks! Should everything in
__all__
from dgl/transforms/functional.py be added to the list in dgl.rst? Also, should they be in the same order? (The ones there at the moment are in a different order than they appear in__all__
.) I can quickly fix up the list. Anything else to add in there?