Daniel Tartaglia

I'll have a look this weekend.

Good catch @Kn1kt. I have updated the test based on your suggestion and updated the code to make the test pass while still passing the other tests. See PR #150

I like this change. It's something that has always bugged me. It should probably wait for the major version bump.

I know this has been an issue since at least 5.0.0 (see for eg: https://github.com/ReactiveX/RxSwift/issues/2098) And I've always used `milliseconds` in production code because of it. So I know none...

Great addition! However, it doesn't handle the optional body correctly. Also, you might consider switching to using `#"..."#` syntax to make things a bit less confusing.

The simplest solution is to add `.delay(.seconds(0), scheduler: scheduler)` to the just... Yes?

Very weird indeed. Especially given that if the body of the closure is only `{ Single.just($0) }` or if it's only `{ Single.just($0).delay(.nanoseconds(Int.random(in: 1 ... 7)), scheduler: scheduler) }`, then...

What is the performance hit? I see if I use: `return Observable.just($0).delay(.nanoseconds(0), scheduler: scheduler)` in the if block it takes 14 seconds to run through the 100_000 elements whereas if...

I'm seeing that if I take your fix and use your initial code, the stack size goes up to 42 but the runtime is only 3 seconds... Looks like a...

> I also believe that scheduler's should be deprecated, and most observables should have their closures marked as async and sendable. I disagree with that. The power of Rx is...