Need some reviews there to merge in case someone can help, thanks!

Hi 👋

master

branch in

arrow

repository has been renamed to

main

branch 🎉 Please, follow these steps to update your local workspace:

git branch -m master main
git fetch origin
git branch -u origin/main main

Thanks!! 🙌

Hi friends! As you know we're paving the road towards Arrow 1.0.0 after latest releases. Something we want to do for the announcement when the time comes (no date yet) is to prepare a short announcement video that I'll not spoil yet, but it would be awesome if we could throw in a pic or short clip representing the Arrow community and the contributors. Probably not everyone in this channel is a contributor but everyone is likely part of the community and would be super welcome. The idea is that we can set a call with lots of people with their camera on so we can take some screenshots or maybe record a bit, who knows. Not required to talk or anything 🙂 it would be around 5 pm CET or something so it works fine for most timezones. Sorry for the spam but if you'd like to help and be on that call please react to this message with a hand up 🙋‍♀️ It will be much appreciated!

Good news everyone! After merging this, now you don’t have to downgrade your JDK version to 1.8 when you want to work on the Arrow codebase aw yeah

Resource parZip & fromAutoCloseable Optimise Github Actions Fix test impl atomic on JS Flow parMap & parMapUnordered I need some help with reviews 😬

Gradle 7.1.1 is now ready to review with support for JDK 16. And AFAIK the website seems to be working ok 🙂 cc: @simon.vergauwen

On other news, this fix is coming to 1.6, which I think will make comprehensions nicer to use 😎

Can we get some 👀 here https://github.com/arrow-kt/arrow/pull/2571

I’ve asked this on the Gradle Slack but no reply 😞 If anyone has any idea that’d be great. The Arrow build is currently broken due to this issue, and we’ve been stuck trying to fix this for quite some time.

Hey everyone,

We have an issue where our Gradle configuration is timing out after 1 minute on Github Actions 😞

I cannot reproduce it locally, but maybe that’s because it’s running fast enough locally. I created this ticket 5 days ago, but haven’t had any feedback.

Has anyone every ran into this issue, and is there any way we could workaround it? https://github.com/gradle/gradle/issues/19446

I’d be happy to PR a fix to Gradle, but not sure what the fix should be. Perhaps a configurable time is sufficient.

Arrow CI timeouts again: https://github.com/arrow-kt/arrow/runs/4776896324?check_suite_focus=true

Can I get a review here just for updating pom definition https://github.com/arrow-kt/arrow/pull/2631?

Can someone take a look here ? https://github.com/arrow-kt/Arrow-MPP-Template/pull/25

Hey all, I wanted to ask if there is a release planned in the near future?

Can we get a review on this https://github.com/arrow-kt/arrow/pull/2692 👀?

Can we get this approved https://github.com/arrow-kt/arrow-integrations/pull/114#pullrequestreview-1321797158 🙂 ?

Hey all, I proposed some new changes for the flattening of

Validated

. There is a series of PRs currently open, and I am looking for feedback. The mapOrAccumulate PR allows binding both

Either<E, A>

and

EitherNel<E, A>

in a single

orAccumulate

DSL. The following introduces the same to all other

orAccumulate

signatures and also removes a lot of code duplication, but also making a small breaking change in the alphas. Specifically here for Either.zipOrAccumulate, the code is now derived from the optimised Raise.zipOrAccumulate. But it works over lambdas instead of values, I also proposed parZipOrAccumulate which matches

parMapOrAccumulate

but for independent operations. The proposed

Either.zipOrAccumulate

now matches the also proposed

parZipOrAccumulate

.

Iterable.mapOrAccumulate

and

NonEmptyList.mapOrAccumulate

are now also derived from the now more optimised

Raise.mapOrAccumulate

. The biggest downside of it all is that without context receivers you need to more often specify type arguments 😞 but their is a very graceful migration from the current encoding to context receivers. You can find a lot more details in the PRs, but feel free to ask and questions or doubts in the PRs themselves ☺️

@julian @Stylianos Gakis I think this YouTrack issue makes

parTupled

obsolete as well. https://youtrack.jetbrains.com/issue/KT-57165 Might be interesting for more people here that are relying often relying on method references in combination with DSLs.

Can I get a review here https://github.com/arrow-kt/arrow-integrations/pull/118 ?

Call for users and use cases for new Arrow website 🗣️ The Arrow team is currently working on a revamped website (to be announced soon), and as part of it we would like to show how our ecosystem is used in practical settings. If you are using Arrow and want to contribute to this new website, we would love to hear from you! Anything from a logo of your company as user to a description to how you use Arrow in particular is welcome. 🎙️ If you want to contribute but are not a fan of writing, I’m more than happy to sit down with you, have a friendly chat, and then write everything down. If you (and your employer) are happy with the result, we’ll then place it in our new Use cases section. 🙏 Thanks in advance for all your help!

I forgot if this is still an issue, but wasn't there problems with

runCatching

swallowing `RaiseCancellationException`s and hence not playing nicely with

Raise

? Should Arrow maybe offer an alternative

runNonFatalCatching

or a

Raise.runCatching

shadowed function that rethrows cancellation exceptions?

Sharing some getting started points for Arrow Exact as a continuation of our discussion on constrained primitives types yesterday. Discussion: https://github.com/arrow-kt/arrow-exact/issues/4 *`PositiveDouble` prototype P*R: https://github.com/arrow-kt/arrow-exact/pull/5

Raised this small PR adding some KDoc around

Raise

https://github.com/arrow-kt/arrow/pull/3038 Motivated by this issue.

Heya @Imran/Malic! I’ve got a PR up to bump kotest version to 5.6.1 for kotest-extensions-arrow. latest kotest requires 1.8.10. https://github.com/kotest/kotest-extensions-arrow/pull/236

@Imran/Malic i’ve got another one for arrow 1.1.5 https://github.com/kotest/kotest-extensions-arrow/pull/237 🎉

hey friends @Imran/Malic master build for kotest-extensions-arrow is currently broken.. i’ve raised an issue https://github.com/kotest/kotest-extensions-arrow/issues/239 The build is currently failing with this error during linux (push).. I can’t reproduce this locally as

./gradlew :commonizeNativeDistribution

succeeded without issue in my mac.. any pointers on how to fix this would be greatly appreciated 🙇‍♀️

> Task :commonizeNativeDistribution FAILED

> Task :kotest-assertions-arrow:compileCommonMainKotlinMetadata
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':commonizeNativeDistribution'.
> Could not resolve all files for configuration ':kotlinKlibCommonizerClasspath'.
   > Cannot resolve external dependency org.jetbrains.kotlin:kotlin-klib-commonizer-embeddable:1.8.10 because no repositories are defined.
     Required by:
         project :

macos (push) steps seems to fail due to missing kotest artifacts which @sam had fixed a while back

Hey folks, can I get a review on this PR? 👀

Just made a PR for a

withError

raise builder, suggested by @CLOVIS, alongside a (surprisingly missing)

Effect.mapError

. There's also a suggestion there as to whether we should have a

merge { }

raise builder or not (which would return a supertype of the raised and returned values, and hence be an analogue for

Effect.merge

)