scalaio logo

The Scala event in France!

November 4th, 2022 - Paris, France
The conference runs from 9:00 am to 6:30 pm
At 8 am, registration will open and a breakfast will be served.

ScalaIO 2022 Program

The CFP is closed.

The schedule will be published soon.

08:00 - 09:00Registration
09:00 - 09:20Introduction
09:25 - 10:20Opening Keynote
10:30 - 11:00TalkTalk
11:05 - 11:35TalkTalk
11:40 - 12:25talkTalk
12h25 - 13:15Lunch break
13:15 - 13:50Quickie
13:55 - 14:35TalkTalk
14:40 - 15:25TalkTalk
15:30 - 16:15TalkTalk
16:15 - 16:35Coffee Break
16:35 - 17:20TalkTalk
17:25 - 18:20Closing Keynote

Talks
Opening keynote
Function reuse is just wishful thinking
Functors, monads, etc... can be both very useful and extremely intimidating. This talk will introduce and justify them in a real life scenario, staying away from their more academic interpretations. It will allow attendants to build a solid intuition for the problems they actually solve.
Cost-effective and easy to maintain GraphQL API integration tests with zio-test and Caliban
Let's study together how Scala, zio-test and Caliban are, each with their own capabilities, helping us in this difficult task of writing and maintaining a production-ready software integration tests suite on a GraphQL API.
Implicit parameters, when to use them (or not)!
Implicits values are one of the unique features of Scala but they are very complex and easy to misuse. So in this talk we will discuss various valid use cases and anti-pattern for implicits. You don’t need to be a Scala expert, I will also present how implicit works at high level.
Category Theory as a Tool for Thought
By rephrasing various FP idioms in the language of Category Theory, we can systematically tackle concepts by deconstructing them and deriving new ideas from them. That is, we can use Category Theory as a tool—a tool for thought.
The Journey of a Dotty Diagnostic
Diagnostics seem simple enough -- you have some message, a position that relates to it, and a severity level. However, what else could diagnostics tell us? How else could we use them? How does a diagnostic even get from the compiler to your editor? Let's follow the journey of a Dotty diagnostic.