Martin Mauch

Implement streaming with state changes

11

This is a draft of a "correct" streaming API where the state changes with the emitted stream elements. @softinio @mtsokol @mijicd could you have a look if this looks plausible?...

Detect duplicate issues

3

The issues section is swamped by duplicates create through Intellij's "Report issue" feature. This Github actions tries to detect duplicates and posts them as a comment with a call to...

Parsing YAML in JS

2

Hi all, I've been having good success using `js-yaml` along with Circe to parse YAML in JS, so I thought I'd post a short comment here: ```scala // build.sbt libraryDependencies...

Use clock package in _TimeIntervalStreamSink (and maybe others)

7

In order to deterministically test async code, the `fakeAsync` package currently seems to be the way to go. Unfortunately, it cannot modify the `StopWatch` from `dart:core`, and instead [it is...

Scala.js compatible version

2

Hi all, I'm trying to make `zio-actors` compile to Scala.js. `zio-actors` uses `zio-config` in quite a few places, so now I'm wondering if it would be possible to make `zio-config`...

Modeling constrained resources

5

Hi all, we have a use case where we would like to model constrained resources (e.g. people or machines) in Baker. Each of these resources has a corresponding token and...

I noticed that there is a whole bunch of `case class`es copied between `com.ing.baker.runtime.scaladsl` and `com.ing.baker.runtime.javadsl`. The only difference seems to be the use of Scala's `Option` vs Java's `Optional`....

Why is Parser0#repSep not possible?

6

Hi all, I'm trying to [port scala-uri to cats-parse](https://github.com/lemonlabsuk/scala-uri/pull/291). One difficulty I'm facing is with parsing path parts including empty ones: ``` a/b/c /a/b/c a//c /a//c ``` What I would...

Different way of combining Parser0 and Parser

1

Hi all! I'm just trying to port scala-uri from parboiled2 to cats-parse. One thing I find rather confusing is the `with1` method to make a `Parser0` behave like a `Parser`....

Tagless Final instead of hard-coded futures

12

I've been digging through the code a little and noticed that the direct use and execution of Futures brings some inconveniences with it: - An `ExecutionContext` has to be passed...