Filippos Christou

and how would you get the vertex metadata ? define a `get_prop` or something ?

so what previously in #39 was done with ``` getindex.([colors], label_for.([colors], inneighbors(colors, code_for(colors, :blue)))) ``` and I wanted it to be like ``` colors[inneighbors(colors, :blue)] ``` with your proposition it...

there is still some space to work before thinking of doing such a mass forwarding which I also find demanding. For example, we could tread `getindex(::MetaGraph, ::Integer)` differently from `getindex(::MetaGraph,...

hm. now that I am thinking about it, it would be good if we could statically dispatch, because probably some function will need different implementation (e.g. rem_vertex should update indices)....

I cannot imagine well about the use cases, but I can also not exclude that someone might want to do this. I am not sure whether we should take this...

Is the plan to migrate `MetaGraphsNext.jl`'s code into `GraphsBase.jl` ?

Hi. To my knowledge there is nothing for MetaGraphsNext.jl. However if you want to read in a MetaGraphs.jl, you can use https://github.com/UniStuttgart-IKR/NestedGraphsIO.jl. NestedGraphsIO.jl can read both NestedGraphs and MetaGraphs.MetaGraph from...

right now the whole GraphsIO.jl thing is a bit of a mess. With julia v1.9 and package extensions things will improve noticeably.

I think the problem is that `MetaGraph{Int, SimpleGraph{Int}, Symbol, Nothing, Nothing, Nothing, e->1.0, Float64}()` will not work. So the empty constructor should be defined in these terms. In that regard...

What about `MetaGraph{Int, SimpleGraph{Int}, Symbol, Nothing, Nothing, Nothing}()`, which currently fails ? I think this empty constructor of the parametrized struct shouldn't fail. e.g. we could define the following constructor...