Tamás Nepusz

I have added an optimized code path for the common case when `g.es.is_all()` is `True` and the selection is based on source or target vertex only. For 0.9.0, we should...

_From @gaborcsardi on March 17, 2015 15:25_ Hmmm, interesting. I had to do some workarounds for the bounds checking, because ARPACK comes up as a false positive. But the workarounds...

_From @rsbivand on March 17, 2015 21:21_ To reproduce, you'd need a recent R-devel (I used 9 March) built normally. Then follow the link to the extensions manual to put...

Unfortunately I'm also a bit lost regarding naming conventions as I only took over the maintenance of the R-igraph package but I wasn't the one who came up with these...

> (@ntamas are you okay with this, or do you think it will overload the issue tracker?) I am in favour; I like "actionable" issues where it is clear when...

PR #437 now contains an interface to `igraph_is_chordal()` (actually, two, `is_chordal()` and `chordal_completion()`)

`C_R_igraph_get_eids` is actually the same as `R_igraph_get_eids`. The `NAMESPACE` file of the igraph R package arranges for all methods listed in the R-C glue code (see `init.c`) to be registered...

Apparently `igraph_get_eids_multi()` still needs you to define the same pair multiple times if you want all edge IDs between them; this is in the C docs: > This function handles...

Not marking the first edge as `true` makes sense depending on the context; in R or NumPy you can use a Boolean vector for indexing, so indexing an edge list...

@szhorvat Re the calling convention: I think it depends on whether you are using `gfortran` or not, and whether you are using sibling-call optimizations. More details in the [R blog](https://developer.r-project.org/Blog/public/2019/05/15/gfortran-issues-with-lapack/index.html),...