Dominik Charousset

> Switching to a set of strings makes sense to me (cc: @Neverlord). No strong opinion either way. On the lower level (BIF), Zeek needs to wrap the strings into...

@awelzel I have tweaked the work-stealing scheduler to avoid spinlocks and `yield()`. Could you check out the branch `topic/neverlord/work-stealing` in your `auxil/broker` and see if that changes anything?

I'm not quite sure what you mean by "improved" `%sys` load. Overall less CPU cycles? That would not be a result of the batching itself, I think. That's probably due...

Yep, there's no other todo.

@shariarriday these should be straightforward to implement as a `step` (like `take`): - First (actually, this is just `take(1)`) - TakeLast - Last (after implementing TakeLast, this is a freeby:...

The `catch` operator is actually more like a family of operators. For example, [RxJava](https://github.com/ReactiveX/RxJava/wiki/Error-Handling-Operators) splits this into `onErrorComplete`, `onErrorResumeNext`, `onErrorReturn`, `onErrorReturnItem` and `onExceptionResumeNext`. We already have `on_error_complete`. We will skip...

~~`Scan` is just another name for `Reduce`, which is already implemented.~~ (edit: mixed something up) I think we can implement `start_with(x)` as `just(x).concat(*this)`. To implement `sample`, we can use the...

@shariarriday I think `retry` is a good candidate to tackle next. Specifically, `retry_when` to retry subscribing to an input observable whenever the "control" observable emits a value. Here's a usage...

To check whether it's still showing up, I ran GCC 11 on macOS today. I didn't see that warning, but similar warnings that look like false positives at a first...

No one actually complained about this in the past 8 years, so it seems like it's not an issue for CAF. Closing.