Skip to content
New issue

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

In Graph, don't keep track of incoming nodes/edges #13

Open
wylee opened this issue Oct 20, 2019 · 1 comment
Open

In Graph, don't keep track of incoming nodes/edges #13

wylee opened this issue Oct 20, 2019 · 1 comment
Assignees
Labels

Comments

@wylee
Copy link
Owner

wylee commented Oct 20, 2019

No description provided.

@wylee wylee self-assigned this Oct 20, 2019
@wylee wylee added the v3 label Oct 24, 2019
wylee added a commit that referenced this issue Nov 15, 2019
@Tristou27
Copy link

Hello @wylee ,

If you have some time to handle my comment, I would like to clarify something about the initial structure of incoming edges. How did that work ? I do not understand how the self._incoming got populated.. I understand that it made use of collections.defaultdict() but not at all how, by creating datas in self._data, the "reverse" was done in self._incoming.

Any cue on that ?
Thanks ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants