Why Infix functions in DSLs in Kotlin? - Purpose & Use Cases

The Big Idea

What if your code could read like a simple sentence instead of a puzzle?

The Scenario

Imagine writing a recipe by listing every step with full instructions and connectors like "then add" or "and mix" explicitly every time. It feels long and clunky, making it hard to read and follow.

The Problem

Writing code without infix functions in DSLs means using lots of dots and parentheses, which makes the code look crowded and hard to understand. It's easy to make mistakes and hard to spot what the code really means.

The Solution

Infix functions let you write code that looks like natural language. This makes your DSL (Domain Specific Language) clear and easy to read, like a simple conversation or recipe, reducing errors and speeding up writing.

Before vs After

✗ Before

val result = add(5, 10)

✓ After

val result = 5 add 10

What It Enables

It enables writing code that reads like plain English, making complex logic easy to understand and maintain.

Real Life Example

Think of a build script where you write "compile kotlin" instead of "compile(kotlin)" -- it feels like giving direct instructions, making the script cleaner and friendlier.

Key Takeaways

Manual code can be hard to read and error-prone.

Infix functions make DSL code look natural and clear.

This improves readability and reduces mistakes.