Gattag

> However I don't understand `[\w.]`. Since `.` matches anything, what's is `\w` doing? Doubtless something as I've no great experience with re. When `.` is inside a character class...

So I realized that there is a slight hiccup in the blocking execution when `ordered=true`, since they are not directly scheduled for execution immediately, a task scheduled on the `ContextScheduler`...

If `ordered` is set to `true`, tasks are scheduled in order of the context so if two workers that share context are created, only one task can run at a...

Specifically, if I ran: ```Java Scheduler s = RxHelper.createBlocking(vertx); Context context = vertx.getOrCreateContext(); context.runOnContext(ignored -> { Scheduler.Worker w1 = s.createWorker(); Scheduler.Worker w2 = s.createWorker(); w1.schedule(() -> /*Runnable A*/); w1.schedule(() ->...

@tsegismont I'm on it. Should the current `ordered=false` impl be maintained as a new third option for legacy reasons or no?

I would also like to note that the scheduler introduces a potential point for drift in the `schedulePeriodically`. The documentation says: `The default implementation schedules and reschedules the Runnable task...

@tsegismont Unless I'm missing something, currently there is no way to provide a custom `TaskQueue` to any `WorkerExecutor::executeBlocking` method and a `Context` cannot be forcibly assigned to the execution of...

>We agreed in previous comments that the current implementation is fine when `ordered` is set to true. So why do we need to change it? So I talked about this...

From my understanding, the usage of `TaskQueue` was placed behind `DuplicatedContext`, now when you call `ContextInternal::duplicate` a new `DuplicatedContext` is returned with its own `TaskQueue` for blocking tasks, but it...

I know this idea gets floated every once in awhile and never gets anywhere, but I think that it would make more sense to improve Kotlin's ability to build such...