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
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem this feature solves
Expose Strongly Connected Component in the CAPI to the PLC and Python API and remove the legacy implementation which doesn't currently support the PLC graph. This align with our long term goal to have all our algorithms to leverage the PLC graph. Once new implementation of SCC leveraging our primitives is available, no change will be necessary in the Python API and only minor changes will be required in the CAPI.
Describe your ideal solution
Remove the legacy strongly connected component from the python API
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
I agree to follow cuGraph's Code of Conduct
I have searched the open feature requests and have found no duplicates for this feature request
The text was updated successfully, but these errors were encountered:
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem this feature solves
Expose Strongly Connected Component in the CAPI to the PLC and Python API and remove the legacy implementation which doesn't currently support the PLC graph. This align with our long term goal to have all our algorithms to leverage the PLC graph. Once new implementation of SCC leveraging our primitives is available, no change will be necessary in the Python API and only minor changes will be required in the CAPI.
Describe your ideal solution
Remove the legacy strongly connected component from the python API
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: