Graphs as custom data types

Question

Graphs as custom data types

Khalian opened this issue 8 years ago · 6 comments

So this does not directly fit the mandate of extensions, but IMO adjacency lists and adjacency matrices are very common data structures that a lot of programmers reuse all the times.

What do you guys think about introducing basic Graph Data structures in this library?

Answer 1 · 2017-02-13T04:18:26.000Z

Definitely makes sense. We'd create new classes? I don't think there's a problem in that since we already have things like the BlockButton, for example

Answer 2 · 2017-02-13T04:19:20.000Z

Yes it would be new classes.

Answer 3 · 2017-02-13T16:08:59.000Z

Also grid system data type will probably useful. But the problem is it will only be used by a very low % of the users. And some people have a concern about unused features polluting the namespace.

So we should either think about it a little more or find a way to address this concern.

Answer 4 · 2017-02-13T17:34:31.000Z

I would necessarily call it a grid. Its more of a representation for graphs.

To avoid pollution of namespaces, we can go with prefixing EZ (e.g. EZEdge or EZNode).

Answer 5 · 2017-02-14T15:06:17.000Z

We could also change the Block stuff into easy as well. Also I think it might be possible to implement the functionality of block buttons as extensions with swifts new version, not sure tho.

Answer 6 · 2017-05-23T02:00:15.000Z

I am not pushing for this since there isn't a terrific use case that warrants it.