You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
e-graph is an important infrastructure for compiler optimisation, are you interested in publishing your related work as an infra module, like egglog?
Once it become stable enough it can serve as an accelerator for various axiomatic rewrite systems (Scala 3 implicit search, Apache Spark SQL Catalyst optimiser, etc.). It can also be sharded using Apache Spark to enable distribute saturation and guided search.
Describe the solution you'd like
If you are interested, I can start working towards a minimalistic PR shortly.
Describe alternatives you've considered
The only Scala implementation I found is LISA prover, tho it will also take some effort to use & publish (epfl-lara/lisa#226)
Additional context
The API of egglog-python can serve as a reference design specification. Comparing to the latest python, Scala is obviously less flexible but has more axiomatic reasoning capabilities. This can be played into our favour
The text was updated successfully, but these errors were encountered:
That sounds like an interesting project. I won't personally work on this, but a PR would be welcome if you manage to pull out the code into a separate repo linking back to this one.
Here are some concerns:
The e-graph and equality saturation implementation of this repo is based on the Rust egg implementation, but has already drifted from the main branch of egg and its latest developments, how would you avoid this problem in the future? Beyond egg, will you reimplement egglog in Scala? Would it make more sense to create a Scala library that interoperates with the Rust libraries?
Features specific to our Rise language needs are currently embedded into this implementation, that are not available in the generic egg Rust implementation, you'll have to think about how to become generic over these without breaking our use case.
I'll start by copying code into an independent Scala 2.13/gradle project and add generic type parameters, hoping that compatibility can be maintained while switching to a more scalable backend.
Upgrade to Scala 3 will be attempted in sync with shine compiler, though I can only hope that it happens fast.
Interacting with rust on diverse hardware architectures was a weak spot of JVM (it may be easier through FFI introduced in Java 22). But there are a few datalog implementations in Scala, some of them can even be distributed on many machines through Apache Spark.
Is your feature request related to a problem? Please describe.
e-graph is an important infrastructure for compiler optimisation, are you interested in publishing your related work as an infra module, like egglog?
Once it become stable enough it can serve as an accelerator for various axiomatic rewrite systems (Scala 3 implicit search, Apache Spark SQL Catalyst optimiser, etc.). It can also be sharded using Apache Spark to enable distribute saturation and guided search.
Describe the solution you'd like
If you are interested, I can start working towards a minimalistic PR shortly.
Describe alternatives you've considered
The only Scala implementation I found is LISA prover, tho it will also take some effort to use & publish (epfl-lara/lisa#226)
Additional context
The API of egglog-python can serve as a reference design specification. Comparing to the latest python, Scala is obviously less flexible but has more axiomatic reasoning capabilities. This can be played into our favour
The text was updated successfully, but these errors were encountered: