You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not clear from the code how NodePosition and some of the other concepts within Node.jl actually work. For instance, are they 0-indexed or 1-indexed? Add some comments to explain these concepts. Eventually, the comments can form the basis of some actual documentation.
The text was updated successfully, but these errors were encountered:
I can work on this over the weekend. But my first priority is to
compose a letter to Brian Arthur that might set up a meeting for late
this month.
Alden
On Fri, Mar 13, 2015, at 18:39, George Lesica wrote:
It is not clear from the code how NodePosition and some of the other
concepts within Node.jl actually work. For instance, are they 0-indexed
or 1-indexed? Add some comments to explain these concepts. Eventually,
the comments can form the basis of some actual documentation.
Reply to this email directly or view it on GitHub: #9
On Sat, Mar 14, 2015, at 01:22 AM, Alden Wright wrote:
I can work on this over the weekend. But my first priority is to
compose a letter to Brian Arthur that might set up a meeting for late
this month.
Alden
On Fri, Mar 13, 2015, at 18:39, George Lesica wrote:
It is not clear from the code how NodePosition and some of the other
concepts within Node.jl actually work. For instance, are they 0-indexed
or 1-indexed? Add some comments to explain these concepts. Eventually,
the comments can form the basis of some actual documentation.
Reply to this email directly or view it on GitHub: #9
Reply to this email directly or view it on GitHub: #9 (comment)
It is not clear from the code how
NodePosition
and some of the other concepts withinNode.jl
actually work. For instance, are they 0-indexed or 1-indexed? Add some comments to explain these concepts. Eventually, the comments can form the basis of some actual documentation.The text was updated successfully, but these errors were encountered: