Use DispatchQueue scheduler

[arunrdd]

The RunLoop scheduler is busy when there is active user interaction(like table view scrolling). All the downstream data updates will be delayed due to this. Using RunLoop works but it would delay network responses, until RunLoop.main is free to process. DispatchQueue scheduler will work just like any other DispatchQueue.main.async blocks.

I haven't simulated this scenario, but it is elaborately discusses in Swift forums. In most cases difference might not be visible. Although, in this framework's context it might be more sensible to use DispatchQueue scheduler.

References:

• https://forums.swift.org/t/runloop-main-or-dispatchqueue-main-when-using-combine-scheduler/26635

[arunrdd]

@s4cha There is I think a mismatch between the Swift tools version this package is using and the one that Github Actions is using to build.

[s4cha]

@ArunRD Thanks a ton for taking the time to document this. According to the swift discussion you provided, this makes perfect sense so let's go for it. I'll try to fix the GitHub job separately, which is more experimental at the moment.

[s4cha]

This should be available in 0.3.1 -> https://github.com/freshOS/Networking/releases/tag/0.3.1 👏