feat(scheduler): removed deprecated queueScheduler constant

BREAKING CHANGE: The `queue` constant is no longer available. Use `queueScheduler`.

Author: demensky

docs_app/content/guide/scheduler.md

@@ -116,7 +116,7 @@ The `async` Scheduler is one of the built-in schedulers provided by RxJS. Each o
 
 ## Using Schedulers
 
-You may have already used schedulers in your RxJS code without explicitly stating the type of schedulers to be used. This is because all Observable operators that deal with concurrency have optional schedulers. If you do not provide the scheduler, RxJS will pick a default scheduler by using the principle of least concurrency. This means that the scheduler which introduces the least amount of concurrency that satisfies the needs of the operator is chosen. For example, for operators returning an observable with a finite and small number of messages, RxJS uses no Scheduler, i.e. `null` or `undefined`. For operators returning a potentially large or infinite number of messages, `queue` Scheduler is used. For operators which use timers, `async` is used.
+You may have already used schedulers in your RxJS code without explicitly stating the type of schedulers to be used. This is because all Observable operators that deal with concurrency have optional schedulers. If you do not provide the scheduler, RxJS will pick a default scheduler by using the principle of least concurrency. This means that the scheduler which introduces the least amount of concurrency that satisfies the needs of the operator is chosen. For example, for operators returning an observable with a finite and small number of messages, RxJS uses no Scheduler, i.e. `null` or `undefined`. For operators returning a potentially large or infinite number of messages, `queueScheduler` Scheduler is used. For operators which use timers, `async` is used.
 
 Because RxJS uses the least concurrency scheduler, you can pick a different scheduler if you want to introduce concurrency for performance purpose. To specify a particular scheduler, you can use those operator methods that take a scheduler, e.g., `from([10, 20, 30], asyncScheduler)`.
 
@@ -146,4 +146,4 @@ Time-related operators like `bufferTime`, `debounceTime`, `delay`, `auditTime`,
 
 Other instance operators that take a Scheduler as argument: `cache`, `combineLatest`, `concat`, `expand`, `merge`, `publishReplay`, `startWith`.
 
-Notice that both `cache` and `publishReplay` accept a Scheduler because they utilize a ReplaySubject. The constructor of a ReplaySubjects takes an optional Scheduler as the last argument because ReplaySubject may deal with time, which only makes sense in the context of a Scheduler. By default, a ReplaySubject uses the `queue` Scheduler to provide a clock.
+Notice that both `cache` and `publishReplay` accept a Scheduler because they utilize a ReplaySubject. The constructor of a ReplaySubjects takes an optional Scheduler as the last argument because ReplaySubject may deal with time, which only makes sense in the context of a Scheduler. By default, a ReplaySubject uses the `queueScheduler` Scheduler to provide a clock.

src/index.ts

@@ -29,7 +29,7 @@ export { AsyncSubject } from './internal/AsyncSubject';
 /* Schedulers */
 export { asapScheduler } from './internal/scheduler/asap';
 export { async, asyncScheduler } from './internal/scheduler/async';
-export { queue, queueScheduler } from './internal/scheduler/queue';
+export { queueScheduler } from './internal/scheduler/queue';
 export { animationFrameScheduler } from './internal/scheduler/animationFrame';
 export { VirtualTimeScheduler, VirtualAction } from './internal/scheduler/VirtualTimeScheduler';
 export { Scheduler } from './internal/Scheduler';

src/internal/scheduler/queue.ts

@@ -7,14 +7,14 @@ import { QueueScheduler } from './QueueScheduler';
  *
  * <span class="informal">Put every next task on a queue, instead of executing it immediately</span>
  *
- * `queue` scheduler, when used with delay, behaves the same as {@link asyncScheduler} scheduler.
+ * `queueScheduler` scheduler, when used with delay, behaves the same as {@link asyncScheduler} scheduler.
  *
  * When used without delay, it schedules given task synchronously - executes it right when
  * it is scheduled. However when called recursively, that is when inside the scheduled task,
  * another task is scheduled with queue scheduler, instead of executing immediately as well,
  * that task will be put on a queue and wait for current one to finish.
  *
- * This means that when you execute task with `queue` scheduler, you are sure it will end
+ * This means that when you execute task with `queueScheduler` scheduler, you are sure it will end
  * before any other task scheduled with that scheduler will start.
  *
  * ## Examples
@@ -65,8 +65,3 @@ import { QueueScheduler } from './QueueScheduler';
  */
 
 export const queueScheduler = new QueueScheduler(QueueAction);
-
-/**
- * @deprecated Renamed to {@link queueScheduler}. Will be removed in v8.
- */
-export const queue = queueScheduler;