An open API service indexing awesome lists of open source software.

https://github.com/polyvariant/scala-git-markers


https://github.com/polyvariant/scala-git-markers

Last synced: 11 months ago
JSON representation

Awesome Lists containing this project

README

          

# scala-git-markers

The worst Scala library you've seen.

## What is this???

This is a realization of a cursed idea based on [this tweet](https://twitter.com/kubukoz/status/1590135952886075393) and [this video](https://www.youtube.com/watch?v=rSk_mea4U1E).

## Usage

In sbt:

```scala
libraryDependencies += "org.polyvariant" %% "scala-git-markers" % "0.1.0"
// For Scala.js, Scala Native
libraryDependencies += "org.polyvariant" %%% "scala-git-markers" % "0.1.0"
```

```scala
import org.polyvariant.gitmarkers._
```

Now, whenever you see git's conflict markers, for example:

```scala
val example = (
<<<<<<< HEAD
"foo"
=======
"baz"
>>>>>>> bar
)
```

you **might** be able to compile your code! Just make sure you define a value for the second ref you're merging (in this case, `bar`):

```scala
val bar = "bar"
```

now you can do this:

```scala
example.describe
// Found conflict:
// - First ref: HEAD
// Value: foo
// - Second ref: bar
// Value: baz
```

## How does this work???

Scala allows you to define symbolic methods. Additionally, you can add extension methods.
The video linked above explains this in more detail.

The desugared form of the conflict above looks similar to this:

```scala
<<<<<<<.HEAD("foo".=======("baz".>>>>>>>(bar)))
```

the rest is done by this library.

## Limitations

This will only work in certain situations, most likely: whenever the conflict encapsulates a simple:

- parameter of a function, or
- expression in parentheses, or
- free-standing expression/statement in Scala 3 or under `-Xsource:3` in Scala 2.13.