CLOVIS
04/13/2023, 3:28 PMstreetsofboston
04/13/2023, 3:31 PMCLOVIS
04/13/2023, 3:33 PMbind
in this example, nor the wrapper return type:
context(Raise<Error>)
fun handlePost(request: HttpRequest): HttpResponse {
val json = request.readJson()
val command = json.toCommand()
val resource = loadResource(request)
val outcome = performCommand(resource, command)
outcome.toHttpResponseFor(request)
}
streetsofboston
04/13/2023, 3:33 PMCLOVIS
04/13/2023, 3:34 PMstreetsofboston
04/13/2023, 3:51 PMCLOVIS
04/13/2023, 3:51 PMstreetsofboston
04/13/2023, 3:53 PMCLOVIS
04/13/2023, 3:53 PMstreetsofboston
04/13/2023, 3:54 PMCLOVIS
04/13/2023, 3:54 PMstreetsofboston
04/13/2023, 3:55 PMCLOVIS
04/13/2023, 3:56 PMEmil Kantis
04/14/2023, 7:27 AMCLOVIS
04/14/2023, 7:39 AMOliver Eisenbarth
04/14/2023, 3:01 PMCLOVIS
04/14/2023, 3:16 PMI would really like to know, if he has seen the latest Arrow API and if he thinks, that this is abusing coroutines and why soConsidering the KotlinX.Coroutines team themselves have praised Arrow for their inventive usage, I wouldn't say it's abuse
Stylianos Gakis
04/25/2023, 7:50 PMeither {}
and the likes.
And a comment that said "bending language features to find a way to achieve the goal" which I assume they meant what Oliver mentions above.
What a weird experience to watch that talk as someone who does actually use arrow and the latest APIs. The problem is that for someone who doesn't, they may just watch this and think "oh okay, so let's not use Arrow then". That was definitely not fun to watch. I guess our best place for feedback is the kotlinconf app which let you write a comment about each talk.CLOVIS
04/25/2023, 10:53 PM