ox

ox copied to clipboard

adamw

`Chunk` is now just a thin wrapper for an Array. It should be optimized to avoid unnecessary copying of data. Operations like concatenation,`drop`, `take`, `splitAt` etc. should be reimplemented. Such...

kciesielski

Ox offers a nice way to manage resources in scopes: ```scala supervised { val serverBinding = useInScope(NettySyncServer().addEndpoints(endpoints).start())(_.stop()) //... never } ``` The release clause (`_.stop()`) is run only if the...

kciesielski

As I discussed with Adam on X, I opened this issue because I tried integrating my library [raise4s](https://github.com/rcardin/raise4s) with Ox. First, I tried to create a custom `ErrorMode`: ```scala 3...

rcardin

Composable retry policies

1

The current retry mechanism allows to provide a single policy for retrying the operation. Once this policy is "exhausted", i.e. when it's done retrying without success, it gives up. We'd...

rucek

Add a schedule-aware repeat

1

While the retry mechanism allows for repeating an operation - according to a `Schedule` in case of error, we'd also like to have a schedule-aware `repeat`, which would run an...

rucek

Mocked time

13

Add `delay` and `now` functions. Add test runtime with emulated clock to test code with delays without spending actual time on delays. Would be invaluable for testing asynchronous code, not...

scf37

Rate control primitives?

1

Hi! At first, thank you for great async library! I tried examples and played exercises using documentation. It was full of fun! My suggestion is providing rate control primitives (e.g....

windymelt

Hey SoftwareMill, Since the introduction of project Loom there is a lot of interest in going back to direct style code from monads. Yet, most of the industry is still...

altrack

The current retry mechanism only supports a single retry policy for a successful/erroneous result of a given operation, which can only be customized by providing a `ResultPolicy` that allows for...

rucek