yes please

that’d be awesome

Raul is more about automating it, but I like the personal touch of writing my own description, which makes it harder to keep up-to-date 🙂

any help received is much appreciated!

Any automated docs are still open to write your own description afaik. Just need to include it in the kdoc along with any runnable snippets. I also like the blogpost style quite more, but of course it's harder to maintain. I have read very good opinions about that blogpost step by step style a bunch of times, so I'd rather keeping and leveraging it if possible

When it comes to learning FP people gets a lot of benefit of that gradual style where you present a use case and iterate over it

I don't think anyone is advising against blogpost /tutorial style docs.

But I think a complete api doc + some tutorials beats a lot of tutorials and a non complete api doc.

In the end tutorials will never cover everything but api docs will

Blog post can go on the kdocs

It's not a matter of choosing style but to using kdocs as the single source of truth so it's maintainable.

Tutorials can go on the kdoc above the class or package

Package MD files are also exported by dokka and kdocs

But please let's move it all to a single place. The sources, so we can maintain it moving forward

https://github.com/47deg/KEEP/pull/16 was discussing in #arrow

not 100% sure that this is what's wanted

I just did the final PR for the IO implementation of the Functional and Reactive domain modeling extras -> https://github.com/arrow-kt/frdomain.kt (it's a fork of the wrong repo but let's ignore that) @pakoito helped a lot with it... any feedback is welcomed 🙂

I just created #arrow-meta for discussions and talk about the arrow-meta project where @Imran/Malic, @Tylos and me are working on

Anyone submitted a talk for Droidcon Berlin?

No, I was asked to but couldn’t

for a second I thought the assignee was the person raising it and I thought "what bad luck to get that same error twice"

it's a shame the commit that fixes the bug isn't linked in the tracker, would like to see what they did to fix it the first time. wonder if they regressed in the recent release

Seem similar to this issue https://github.com/nomisRev/kotlinc-inference-bug

It’s been reported a bunch of time also with non-Arrow examples

Maybe if enough people complain it will be fixed 😁

@pakoito @raulraja @simon.vergauwen https://github.com/arrow-kt/arrow/pull/1453 - adds `.tupled()`/`.untupled()`

Wasn't sure how to assign reviewers/etc. or if you did that. Let me know what changes you need or anything else I've missed

@Bob Glamm why does it say that the commits are by https://github.com/glammr1?

work vs. personal account. I was hoping they were all going to be represented as 'glamm' but I guess not