RFC: New Denops interface for passing AbortSignal

[lambdalisue]

Related to #415

To pass AbortSignal to methods of Denops, I'm wondering a new interface like

export interface Denops {
  // ...

  redraw(force?: boolean, options?: { signal?: AbortSignal }): Promise<void>;
  
  call(fn: string, args: unknown[], options?: { signal?: AbortSignal }): Promise<unknown>;
  
  batch(calls: [string, ...unknown[]][], options?: { signal?: AbortSignal }): Promise<unknown[]>;
 
  cmd(cmd: string, options?: { ctx?: Context, signal?: AbortSignal }): Promise<void>;
 
  eval(expr: string, options?: { ctx?: Context, signal?: AbortSignal }): Promise<unknown>;

  dispatch(name: string, fn: string, args: unknown[], options?: { signal?: AbortSignal }): Promise<unknown>;
}

But this is an interface breaking change that we should try hard to avoid while users may want to use denops plugins that followed or doesn't followed this breaking change in same time.

So we may need to add new methods like

export interface Denops {
  // ...

  redraw2(force?: boolean, options?: { signal?: AbortSignal }): Promise<void>;
  
  call2(fn: string, args: unknown[], options?: { signal?: AbortSignal }): Promise<unknown>;
  
  batch2(calls: [string, ...unknown[]][], options?: { signal?: AbortSignal }): Promise<unknown[]>;
 
  cmd2(cmd: string, options?: { ctx?: Context, signal?: AbortSignal }): Promise<void>;
 
  eval2(expr: string, options?: { ctx?: Context, signal?: AbortSignal }): Promise<unknown>;

  dispatch2(name: string, fn: string, args: unknown[], options?: { signal?: AbortSignal }): Promise<unknown>;
}

But you know, it looks horrible. Does anyone has more brilliant idea for this?