zio-protoquill VS LiveTyping

There is: https://github.com/zio/zio-protoquill

Among Scala 3-only macro codebases is proto-quill (Quill for Scala 3). Other than that most libraries will be cross-compiled Scala 2 and Scala 3 because they have to cater to both long-time Scala 2 users as well as those who already migrated.

Proto Quill, a query DSL similar-ish to Slick, is certainly the poster child of what's possible with Scala 3 macros.

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.

I am a Scala engineer and have upstreamed a lot of open source projects to do this, (i.e. see https://github.com/getquill/protoquill/pull/17). Basically its a github action that runs concurrently to the main build, this has the following advantages

I've been refreshing https://github.com/getquill/protoquill nearly every day!

Hernán Wilkinson will be our host. He will present LiveTyping: Automatic Type Annotation for Dynamically Typed Languages. Introduction to the concept. Possibilities. Demo.

IDE Assistance? Smalltalk had it early and continues to evolve it to new heights - lately with experiments in Live Typing

There are more ways to ensure correct code than manifest static typing. There are editors that will assist you in the construction of correct code that do not rely on old school static typing. Live Typing for instance uses a vm that examines running code and determines things like actual return types for methods on classes and what types are most frequently passed for arguments and feeds that information to the editor to generate warnings to the programmer when they are writing code that may be questionable. These are just editor style warnings but they provide additional feedback to the programmer that the code they are writing may not work as expected. This is what you really want. Help constructing correct code. Here is a talk explaining it in more detail.

Currently, almost all mainstream dynamically typed languages support type annotation a la Strongtalk. Python calls it "type hints", TypeScript is JavaScript+type annotations, PHP calls it "type declarations" and Ruby does it through a tool called Sorbet. All of them annotate the types in the source code and it is the programmer who must write and maintain the annotation. In all cases, it is not mandatory for the system to correctly type check for it to run. LiveTyping is a type system proposal for Smalltalk, that seeks similar objectives but implemented in a different way. First, it is the environment itself that collects and maintains the types based on the execution of the system, not the programmer. Second, the types are not interleaved in the source code, thus maintaining the syntax and simplicity of the language. And finally, the main objective is not to carry out a static type checking (although it supports it), but to augment the programmers experience increasing the usability of current tools such as searching for senders and implementers, and performing more accurate and safe refactorings. In this talk Hernan will briefly show how LiveTyping is implemented to later concentrate on the improvements made to the tools and the benefits it brings when developing software with Smalltalk. LiveTyping is currently implemented in Cuis Smalltalk and has been successfully used for the last two years in three different universities in Argentina when teaching Object Oriented Programming and Design.