Tamás Nepusz
Tamás Nepusz
Interestingly enough, the leak is not there if I set `igraph_options(return.vs.es=FALSE)` - which means that the leak is not in the shortest path routine where I initially suspected it to...
An even simpler way to trigger the issue (no graphs involved): ``` library(igraph) iterations
Note to self: each igraph object contains a hidden _environment_ that is used to record mutable meta-information about the graph without changing its identity. igraph vertex sequence objects (i.e. ones...
Retargeting this to a later milestone as it's unlikely that we can sort this out before the release of 1.3.0 -- it would require us to find a replacement for...
Okay, I have a patch for this now but I'll hold it off until 1.3.2 is out because this can potentially break reverse dependencies if they happened to use a...
I have fixed the above, except the ones in `structural.properties.R`. There I feel that a cleaner solution would be to introduce an extra argument next to `na_ok`, something like `resolve_attrs...
Commit 4ccd00f7 adds a `resolve_attrs=...` option to vertex / edge indexing so you can turn attribute lookup off in problematic cases.
I'm not familiar with `rlang::.data` -- can you point me in the right direction in the docs to see how it is supposed to work?
Nice, I like the idea of the disambiguation prefixes now that I learned about them! I still need to read up a bit on R environments and stuff to get...
Yes, if we decide to go down this road, then `resolve_attrs` is not necessary. I'll experiment with this later today.