dotty VS Quill

A more limited way to do runtime evaluation is via the jsr-223 support: https://github.com/lampepfl/dotty/blob/main/tests/run-with-compiler/scripting.scala, you can't reflect on types that way but the advantage is that you don't end up depending on compiler-internals APIs that could change in any patch release.

https://github.com/lampepfl/dotty/issues/14262 points to https://github.com/invesdwin/invesdwin-context/blob/master/invesdwin-context-parent/invesdwin-context-scala/src/main/java/de/invesdwin/context/scala/pool/WrappedScalaScriptEngine.java which seems to be doing some caching via https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html, but I have zero experience with this stuff.

Note though that our jsr-223 support is currently a bit limited compared to the scala 2 version: https://github.com/lampepfl/dotty/issues/14262

If you could open an issue at https://github.com/lampepfl/dotty/issues detailing your problems with the bash shell on Windows that would be useful (it's likely our scripts have only been tested with the cmd.exe shell).

That seems like a bug. Could you open an issue at https://github.com/lampepfl/dotty/issues?

- If you can't generate a quotation and need any strings, then the next option - add compiler to the classpath and use JSR223 scripting API: (example : https://github.com/lampepfl/dotty/blob/master/tests/run-with-compiler/scripting.scala

The main blocker for such libraries is https://github.com/lampepfl/dotty/issues/11685 now, that also blocks cats-tagless, and hopefully it will be fixed in near future. So if you can wait several months, it would be the easiest choice... so do I :)

See https://github.com/lampepfl/dotty/issues/13985, maybe the graalvm reflection config format could be enriched to support wildcards if it doesn't already?

I think Quill is the closest to your request: https://github.com/zio/zio-quill

If this still looks like too much hassle, you can always go a bit higher-level and use something like Quill, which is also a powerful approach that uses a different, more ORM-like style.

I'm using it mostly for full-stack web development with ScalaJS (https://www.scala-js.org) in the frontend (https://outwatch.github.io/docs/readme.html) and in the backend with AWS lambdas.

The ecosystem is currently in the process of porting all the libraries to Scala 3. So if you're new to Scala, I'd recommend to start with Scala 2, which is rock-solid and already very powerful.

I never worked with SQLAlchemy. But on the scala database side, popular libraries are Doobie (https://tpolecat.github.io/doobie) and Quill (https://getquill.io). Keep in mind that these are for Scala on the JVM. On the ScalaJS side I'm using the javascript library pg. But I'd like to try if it works well with Prisma soon.

The nice thing about ScalaJS is, that you can use Javascript libraries. And if there are typescript facades, then you can transpile these to Scala and use them in a type safe way (https://scalablytyped.org).

I know that libraries like Scodec and shapeless were rewritten practically from scratch for Scala 3, taking advantage of the next syntax and internals, as well as protoquill - a Scala 3 implementation of Quill.

Akka HTTP, Cats, Quill, ninny, Monix Observable, mill.

https://github.com/getquill/quill is my choice. Works like a charm.

https://getquill.io/#docs (Look under SCHEMA).

I would use it at work because I know it. There are a LOT of libraries in Scala for HTTP up to database stuff, and it really depends on what kind of ecosystem you're walking into:

* Scala as Python: https://github.com/com-lihaoyi/cask, maybe https://github.com/getquill/quill

* Scala as Haskell: HTTP4s, https://tpolecat.github.io/doobie/

* Scala as Rails: Play

Play is the closest thing to Rails-like CRUD productivity IMO, and honestly for CRUD most times I would like to write as little code as possible and just get it done, even using low/no-code solutions (postgrest, hasura, htmx), but that wasn't the question :)

quill is uses type level programming. It allows for the pre-computation of SQL queries during compilation, and you can inspect what queries will look like, whilst you code without, running anything.

I've heard that too but I think there are at least efforts to support Scala 3.

Having said that I think Quill looks nicer (https://getquill.io/) if you want a DSL like that.