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

Label Restructuring #21

Open
IMP1 opened this issue Jul 6, 2018 · 0 comments
Open

Label Restructuring #21

IMP1 opened this issue Jul 6, 2018 · 0 comments

Comments

@IMP1
Copy link
Owner

IMP1 commented Jul 6, 2018

Marksets on an edge's label are not maintainable. At all. This seems bad to me, as the label's value is maintainable, using a variable. Should there be a convenient way to reference a markset? This seems like a lot of additional complexity (is a markset its own type? is it an array of marks, which are their own type?).

Perhaps marksets should be gotten rid of. Is a single label value enough? Another type (colour or style or something) could be added.

Maybe it needs to be a list of values. But then the same problem arises, there's no way to keep the rest-of-the-list of an edge's label. Only whichever variable you've matched on.

What's the use case for multiple values?
I think I can see a use-case for having both a value, and some styling/debugging information, or some marker of a 'head' node or edge. And maybe the current markset is fine for that goal.

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

No branches or pull requests

1 participant