[DOC]: C API doc strings don't always make sense with python bindings

Is this a duplicate?

• I confirmed there appear to be no duplicate issues for this bug and that I agree to the Code of Conduct

Is this for new documentation, or an update to existing docs?

Update

Describe the incorrect/future/missing documentation

cuda-bindings turns some c api arguments into returns, and yet it still reuses C API doc strings that don't make sense. See e.g. on enclosed screenshot, `from and to may both be NULL`, but user doesn't control `from` and `to` so user cannot set them to NULL. There's also broken formatting where things that should not be italicized are italicized. The doc should be something like "if numEdges is 0, `to` and `from` are returned as empty lists, and the function only returns the number of edges in `numEdges`. Otherwise, `to` and `from` will have `numEdges` entries" NULL also doesn't make sense in python context.

If this is a correction, please provide a link to the incorrect documentation. If this is a new documentation request, please link to where you have looked.

No response

Inizia individuando la documentazione rivolta a Python che riutilizza le stringhe della C API mostrate nello screenshot, quindi confronta le descrizioni dei parametri e dei valori restituiti con il comportamento del binding. Il lavoro è completato quando la documentazione interessata descrive le liste restituite e i valori Python anziché argomenti C controllati dall’utente o NULL, con la formattazione corretta.