The general theme of this seems to be: Reduce boilerplate with compiler macros. This is pretty similar in functionality to Slick. From reading the docs, it see

The general theme of this seems to be: Reduce boilerplate with compiler macros. This is pretty similar in functionality to Slick. From reading the docs, it seems like it reduces some of the boilerplate (eg. in Slick you need to define both case classes and tables) but at the cost of potentially less customization. Additionally, while Slick has a layer that you can use to actually create your database tables, this appears to be query layer only. That isn't a problem, I think. I found Slicks ddl stuff was mostly an antipattern in production (you should use an actual migration framework). Another big advantage Quill has over slick is how easy it is to see the resulting query.