-
Notifications
You must be signed in to change notification settings - Fork 69
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
Use rewrite rules instead of some specialization #93
Conversation
@nobrakal Awesome, thank you! Will the same come for non-empty graphs? |
I think yes, as well as many So since we make no use for now of rules pragma in (In fact, I already added almost all of these rules in |
Right, I see. We could split the work on non-empty graphs into a separate PR.
Are these essentially the same as in this PR? In this case, I think it makes sense to combine all such changes together in one PR. Do you agree? If yes, I'll wait for further commits. |
Yep this is mainly specialize and rules pragma. In fact, it would be great to add these pragmas directly into the |
If you manage to do this at the |
You were right, I was a bit optimistic... I as not able to sneak this into the So I think it is a good idea to open an other PR concerning non-empty graphs, since there will be some different work unrelated to |
OK, sounds good. Then I'm waiting for further |
I do not have any :) Do you see anything missing for |
Ah, I think I just misunderstood one of your earlier messages :) Merged now! |
Hi,
Trying to improve the
MaybeNonEmpty
version, I discovered that the rewrite rules are very powerful foredgeList
(it comes from the quickness of AdjacencyIntMap):edgeList
Description: Produce a list of the edges in the graph
Mesh
Clique
Circuit
SUMMARY:
ABSTRACT:
(Based on an average of the ratio between largest benchmarks)