shit, thought this might happen

can’t add this extension method

e: /Users/kevin/Development/GitHub/kategory/kategory-core/src/test/kotlin/kategory/data/TryTest.kt: (71, 24): Cannot choose among the following candidates without completing type inference: public fun <B> Try<Int>.getOrElse(default: () -> Int): Int defined in kategory public fun <B> Try<Int>.getOrElse(default: (Throwable) -> Int): Int defined in kategory

erasure

name it differently

rename the old one to getOrDefault

change the tests and docs accordingly etc

changing API a luxury allowed by being a 0.x version?

i think 99% of calls to getOrElse will work with the new overload

someone would have to be calling

getOrElse(foo)

where

foo

was explicitly typed as

() -> T

, rather than what most call sites will be doing, which is

getOrElse { ... }

i’ll tinker with it, thanks

changing API a luxury allowed by being a 0.x version?

Yes, pretty much. We still have a bunch of stuff to get ready before release so none of the APIs is expected to be stable ATM.

@pakoito uploaded a file:

600 stars and a spoiler alert 😄

xD

Whats with the name change?

is a surprise!!

Why arrow? Kategory made sense to me, whilst arrow seems meaningless (and I am not looking forward to googling for arrow + X, similar to Chef)

Everything will be explained on its due time

I think the PRs give it away 🙈

shh, is a secret 🙊

not sure what they mean by the

arrow

structure

I’m assuming https://www.haskell.org/arrows/

It’s the exact same theoretical concept

ah

thank you

that makes sense

Through this and the PR, one should understand the name change, but I won’t speculate since they seem to want to remain secretive. 😉

should I be able to build right now on HEAD of master?

right now the :detekt task is failing