We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Here's one option for making working with labels easier:
Right now we have for example Graphs.outneighbors(meta_graph::MetaGraph, code::Integer) and outneighbor_labels(meta_graph::MetaGraph, label).
Graphs.outneighbors(meta_graph::MetaGraph, code::Integer)
outneighbor_labels(meta_graph::MetaGraph, label)
Maybe we could have a general pattern where we add a _labels suffix to a Graphs function to make it work with labels instead of code?
_labels
Graphs
We could then have a @labels macro that attaches the _label suffix to all surface-level Graphs function calls?
@labels
_label
The text was updated successfully, but these errors were encountered:
Not bad! Related: #59
Sorry, something went wrong.
No branches or pull requests
Here's one option for making working with labels easier:
Right now we have for example
Graphs.outneighbors(meta_graph::MetaGraph, code::Integer)
andoutneighbor_labels(meta_graph::MetaGraph, label)
.Maybe we could have a general pattern where we add a
_labels
suffix to aGraphs
function to make it work with labels instead of code?We could then have a
@labels
macro that attaches the_label
suffix to all surface-levelGraphs
function calls?The text was updated successfully, but these errors were encountered: