ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #scala
Opaque types let a Scala 3 module expose a compile‑time distinct type while keeping a primitive representation at runtime. This note walks through requirements, minimal design, trust boundaries, operational checks, failure modes, and when to adjust the design.
Learn how Scala 3’s opaque types let you distinguish domain values like UserId from OrderId at compile time, keep runtime representation lightweight, and still integrate with your existing code. A practical example, trade‑offs, and verification steps are included.
Learn how Scala 3's given and using clauses replace the overloaded implicit keyword to provide clearer dependency injection and type-class resolution.
Use Scala custom extractors (unapply) to extend pattern‑matching safety to any class, keeping exhaustivity checks and expression‑oriented code without instanceof casts.
A diagnostic guide for Akka Cluster Sharding entities that never receive messages: registration gaps, passivation recovery failures, serializer mismatches, and how to verify each fix.
A concise diagnostic guide to identify, understand, and resolve StackOverflowError caused by deep, non‑tail‑recursive functions in Scala. Includes checklists, refactor patterns, and verification steps.
Decide whether to use Scala 3's built‑in enum or a sealed trait for a closed set of cases. The article compares features, trade‑offs, and shows a concrete example with validation steps.
Learn how Akka Typed Actors enforce message contracts at compile time, reducing runtime casts and making actor‑based systems safer to refactor.
Learn how to use Scala 3 opaque types to eliminate primitive obsession and prevent domain logic errors with zero runtime overhead.
akka