Off-the-wall question (and I apologize for my ignorance in advance, I have been living under a mountain of work for the last month and have not had time to keep up with arrow-meta), will arrow-meta enable us to create plugins that accept Spock-like syntax? E.g.

fun userAcceptanceTest() {
   given:
   setup()
   and:
   otherSetup()
   when:
   someAction()
   then:
   someAssertion()
   1 * someService.gotCalled()
   where:
   my |  data | fields
   1  | "foo" | false
   2  | "bar" | true
}

? Or is that too far away from mainline Kotlin syntax for that to happen

I don't think extending parser is something arrow-meta currently does. However, if you Kotlin-ify existing example, it does not look that bad from my perspective:

fun userAcceptanceTest() {
   given {
       setup()
   }
   and {
       otherSetup()
   }
   when {
       someAction()
   }
   then {
       someAssertion()
       1 * someService.gotCalled()
   }
   where {
       // probably some infix magic here
       my |  data | fields
       1  | "foo" | false
       2  | "bar" | true
   }
}

@Bob Glamm now that is an interesting idea - it almost feels like sqldelight in a way but for testing: https://github.com/cashapp/sqldelight

Agree re: Kotlin-style syntax, esp. since it's just a matter of defining

fun .. where((..) -> ..)

@Bob Glamm see this thread for an example! https://kotlinlang.slack.com/archives/CJ699L62W/p1576079902008100?thread_ts=1575675759.478700&cid=CJ699L62W

At the moment we are not augmenting parsing though it’s possible. If someone is interested in alterations to parsing and grammar is not something Arrow plans to do for itself as it would deviate from Kotlin and to the contrary we are making arrow more safe and more close to vanilla kotlin than ever even eliminating redundant datatypes

oops - so sorry, I misread this one a bit, yes, thank you @raulraja for the clarification.

no worries, just adding some additional context

@Bob Glamm another consideration is that you can create a similar idea with infix operators and DSLs, a feature that already exists in Kotlin as well in order to achieve the same thing, if the purpose is to create only special sugar syntax for internal use ❤️