Open issues for 2.x
See original GitHub issueHi @peter-empen,
the README mentions the improvements in the 2.x branch and especially the simplified type signatures might be helpful in our Petri Net library Kagera.
You also mention that a lot is left to do there.
The tests are all green, so the core part looks good.
Is it the commented out dot
and json
sub-projects that need to be made working, or is there something else left to do?
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
About issues - GitHub Docs
Use GitHub Issues to track ideas, feedback, tasks, or bugs for work on GitHub. ... To help contributors open meaningful issues that provide...
Read more >Vehicular Communications: Standardization and Open Issues
This article analyzes the ready-to-deploy DSRC and the promising LTE-V2X, compares them according to a set of significant technical and non-technical aspects, ...
Read more >List of unsolved problems in mathematics - Wikipedia
Many mathematical problems have been stated but not yet solved. These problems come from many areas of mathematics, such as theoretical physics, ...
Read more >Issues | Open Journal Systems
As an Editor you have four issue-specific pages available: Create Issue, Notify Users, Future Issues, and Back Issues. ojs2-1-issues.
Read more >Issues for all projects | Drupal.org
Project Title Status Priority
Entity Access by Role Field Drupal 10 compability adjustments Needs review Nor...
Commerce Core Error: Call to a member function getState()...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI I’m working on “2. Drop Scala 2.12 compatibility” now.
It would be great if you found time to work on the unfinished parts. Some suggestions:
core
first.State.scala-
back toState.scala
and make it compile. Refactor the accompanying test. To testState
in isolation may require some more sophisticated test setup, though.GraphTraversal.scala-
back toGraphTraversal.scala
and make it compile. For the missing pieces try using???
temporarily.GraphTraversalImpl.scala
- andTraverserImpl.scala-
.At this point you are almost done and, having bocome a Graph4Scala expert, you are able to continue on your own. 😄