@pakoito last time I checked there are a lot of cases where it is not the case.

there are, and we should address it hahaha

Okay 😄 I agree

I tried to clean it up on the files I've visited lately, not project-wide yet

so the key idea is that inputs are always the Kind alias

and outputs are always the concrete type

in any place where it makes sense

so flatMap isn't

(A) -> Option<B>

but

(A) -> OptionKind<B>

That encoding is necessary por @deriving among others since it forwards implementation for the type class instance delegating to the datatypes and the typeclass as expressed can only be done over `HK`s

@pakoito Does the receiver constitute as an input?

so, should we define

fun <A> TryKind<A>.map(f) = ...

instead of

fun <A> Try<A>.map(f) = ....

@pablisco Since

Try<A> : TryKind<A>

it's always preferable to define them over the kinded representation

that way users avoid having to

.ev()

later (they have to any way because Kotlin does not support HKs but not as often)

That was my thought, I'll update

Weak

accordingly then 🙂

buenos dias a todas y todos

what can I do to contribute to try.arrow-kt.io ? ^^

Hi @jmfayard! We have a fork in the org at https://github.com/arrow-kt/try.arrow-kt.io that we need to do two things with at this moment: 1. Attempt to run it locally to set it up for development 2. Make it easier to develop by simply adding a gradle task that bootstraps the server and web client 3. Document all the process in the README for others to be able to contribute 4. Add the latest stable arrow artifact dependencies to the classpath in that project so that when it loads the code snippets it can resolve the Arrow classes

@pguardiola and myself can also help along the way clarifying

Once we have those steps completed we are gonna modify

ank

which is is our documentation compiling and evaluating tool to export the docs in the format that

<http://try.arrow-kt.io|try.arrow-kt.io>

expects as part of the CI build.

The end goal is to setup an automated pipeline such as that when the docs are merged into master we autogenerate the exercises and deploy the site. The docs will link to each exercise in

<http://try.arrow-kt.io|try.arrow-kt.io>

and the other way around.

ok! ping me when I can be useful

@jmfayard whenever you are ready if you want to help with those steps. We have not gotten started yet.

I’m working on improving comprehensions to better support multiple threads and a nicer syntax

with fewer ambiguities

the first PR is out now

this PR makes it so you don’t have to call yields() to return from a binding comprehension anymore

we capture the return value of the block and use that value as the last return of the datatype