Milestone: Scala 3 (Dotty) Support

[xerial]

Scala 3 (dotty)

• Use Scala 3.0.0 Upgrade to Scala 3.0.0 #1639
• Add a basic configuration
• Extract AirSpec as an external project Build AirSpec using a sub project #1992
• Test Scala version sandwitch Implement Scala 2.13-3.0 sandwich sbt/sbt#5767
• airframe-log support [WIP] Dotty support #867 airframe-log: Dotty support #1381
• Surface support [WIP] airframe-surface Dotty support #1384
  • Surface.of[X] airframe-surface: Support Surface.of[X] for Scala 3 (Dotty) #1385
  • Surface.methodsOf[X] airframe-surface: Surface.methodsOf[X] for Scala 3 #1403
• airframe-di support airframe-di: Next generation DI library #1649
  • Split source folder for Scala 2 and 3 airframe-di: Split Scala 2 and Scala 3 source folders #1405
  • Support Scala3 macros airframe-di: Add Scala3 impl base #1407
  • deprecate in-trait bindings airframe-di: Next generation DI #1653
  • [ ] new A with DISupport airframe-di: Support generating a new instance A with Scala 3  #1410
  • [ ] Traverse Template node in Scala 3 for rewriting new A with DISupport {} code TreeMap doesn't traverse Template class scala/scala3#10931
• AirSpec AirSpec: Scala 3 support #1659
• Use TastyInspector
  • Create ReflectSurface factory
  • RuntimeSurface.of[X]
• Run all AirSpec tests
  • parquet airframe-parquet: Scala 3 support #2209 Need to resolve Surface of nested objects at runtime or pre-register Surfaces
  • grpc (Need to register trait factories to start gRPC server. airframe-http-router/grpc: Scala 3 support #2194
    • Scala 3.1.3-RC2 or later will be required for generating new class from a trait type T Quotes: generate arbitrary trait or class implementations scala/scala3#11685)
  • airframe-log
  • surface
    • recursive surface (with type substitution)
    • local surface inside object or class airframe-surface: Support local class surfaces for Scala 3 #1695
    • NamedParameterTest
    • RecursiveHigherKindTypeTest [surface] Scala 3: Pass all tests on JVM #2052
  • di
  • codec
  • json
  • msgpack
  • canvas
  • control
  • ulid
  • metrics
  • rx
  • okhttp (Finagle server is used for testing) airframe-http: Deprecate the legacy HttpClient[F[_], Req, Resp] interface #2440 airframe-okhttp: Scala 3 support #2865
  • http-recorder (Finagle server is used internally) airframe-http-recorder: Use standard interface based on HttpMessage.Request/Response #1146
• airframe-config
• airframe-http
• airframe-http-router
• airframe-http-grpc (codec is required)
  • airframe-http-router
  • airframe-http-codegen (Need to read Surfaces of RPC/Endpoint interfaces from classpath)
    • Fix (or remove the usage of) unstable Tasty-based surface airframe-surface: ReflectSurfaceFactory.ofClass(cl) causes illegal multithreaded access to ContextBase error in Scala 3 #1698 See also Milestone: Airframe 22 #2006 for more context
• [ ] airframe-http-finagle (Finagle must be migrated to Scala 3) Finagle will not migrate to Scala 3 soon
• canvas
• codec
  • Split code for Scala 2 and 3 airframe-codec: Scala 3 support #1640
• control
• jmx
• launcher
• metrics
• msgpack
• json
• rx
• rx-html
• rx-html-widget
• parquet
• ulid
• Cross build for Scala.js + Scala 3.0.0
  • Extract sbt-airframe as a separate project Extract sbt-airframe as a separate GitHub project #1686
  • Surface (Use Scala 3 inline methods for JS src) AirSpec: Scala.js + Scala 3.0.0 prep #1676
  • AirSpec for Scala.js + Scala 3.0.0 AirSpec: Scala 3 + Scala.js support #2202

[deabreu]

Hi, I'm researching alternative frameworks for web development in Scala, as I want to move away from Akka, which would include Play and Lagom.

A few weeks ago, I've come to know Airframe and the possibility to move to Scala 3 caught my attention.

I see this is not completed but much of the work is done already. So I want to ask if you think it should be ok to start a new project in Airframe using Scala 3 only.