divVerentNov 11, 2022
sc 

#Git conflict syntax is valid #Scala syntax lmfao 😂

Just use #Clojure everyone. Please.

#Programming

https://twitter.com/kubukoz/status/1590135952886075393

Jakub Kozłowski 🐀 @[email protected] on Twitter

“I'm pleased to announce that git conflict markers are parsed as valid Scala.”

Twitter
Nov 10, 2022 at 9:30pmWeb
Show threadIvan Sagalaev Nov 10, 2022
@sc to be precise, it's not git conflict syntax. It's been used at least in svn before, too. It's more like a universal conflict syntax :-) I remember horror hypotheticals "what if there was a language where it was valid"… And here we are :-)
Show threadCarlo ZancanaroNov 10, 2022

@sc How exactly does #clojure save us here?

Try adding this before that same conflicting block. Clojure will happily evaluate it without an error.

(declare <<<<<<< ======= >>>>>>> HEAD git1-a)

I don't think this is a dunk on #scala. This is basically "we taught the Scala compiler how to understand git conflict markers, and it believed us!"

Show threadMarcin Szałomski 🌀Nov 11, 2022
@sc Clojure is awesome, sure. Anyway, I guess you know that what you showed is a joke and one implemented a "support for conflict" that you see in the screenshot. It's only about the flexibility of #Scala and any DSL you can easily implement.
Show threadlachezarNov 11, 2022
@sc once you define all the functions anything can become valid Scala, I don’t see this as a reason to use any other language (maybe even the contrary 🤷)
Show threadThiloNov 12, 2022
@sc Scala as better Java, Scala as better Python, Scala as Poor Man‘s Haskell, and now Scala as the new Perl?