You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This request has been made multiple times, but I couldn't find an issue for it so I'm creating this.
Users have requested (a recent hackathon was one know example of such a request) a simple "hello world" style C++ example that uses libcugraph. For now, we've been recommending the C++ unit tests, but these aren't optimized for demonstrating the API as much as they are just achieving test coverage.
One option could be to simply change the unit tests so they demonstrate the API better, or add additional tests that are better suited as examples and leave the other, harder-to-read tests in place for covering edge cases and other test scenarios. This is nice because it guarantees the examples work with the latest code changes since they'll be run as part of CI.
+1 - This would be very helpful for people who are already using libraries like boost::graph to understand for what use cases they should or shouldn't think about adopting libcugraph.
This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.
This request has been made multiple times, but I couldn't find an issue for it so I'm creating this.
Users have requested (a recent hackathon was one know example of such a request) a simple "hello world" style C++ example that uses libcugraph. For now, we've been recommending the C++ unit tests, but these aren't optimized for demonstrating the API as much as they are just achieving test coverage.
One option could be to simply change the unit tests so they demonstrate the API better, or add additional tests that are better suited as examples and leave the other, harder-to-read tests in place for covering edge cases and other test scenarios. This is nice because it guarantees the examples work with the latest code changes since they'll be run as part of CI.
cc @ogreen
The text was updated successfully, but these errors were encountered: