On Thursday, 11 July 2013 at 18:42:10 UTC, H. S. Teoh wrote:
However, I think we should also provide friendlier representations for user-facing types. One possibility is a wrapper type that accepts string IDs for nodes/edges, and internally maintains a mapping between them and
numerical IDs, so that the user doesn't have to keep doing this
manually. This way the algorithms can run at top speed, and the user can
still get a nice API for string-based IDs.

Yes, I agree. The goal right now is to get the internal stuff really well done, with a friendly face to follow.

Reply via email to