Consider defining default methods on prototype

[vweevers]

To make TypeScript stop complaining about undefined types, instead of:

AbstractChainedBatch.prototype.put = function (key, value) {
  // ..

  // @ts-ignore
  if (typeof this._put === 'function') {
    // @ts-ignore
    this._put(key, value)
  } else {
    this._operations.push({ type: 'put', key: key, value: value })
  }

  // ..
}

We could write:

AbstractChainedBatch.prototype.put = function (key, value) {
  // ..

  this._put(key, value)

  // ..
}

AbstractChainedBatch.prototype._put = function (key, value) {
  this._operations.push({ type: 'put', key: key, value: value })
}

Same with all the other methods. Thoughts @ralphtheninja @juliangruber?

[vweevers]

@ralphtheninja such a change could be a patch release, right? It doesn't change behavior, unless someone is doing some funky prototype stuff (I wouldn't know what).

[ralphtheninja]

Aye, a patch version should be sufficient.

[vweevers]

We have a weird one here:

abstract-leveldown/abstract-chained-batch.js

Lines 79 to 85 in 0d942fd

	if (typeof this._write === 'function') { return this._write(callback) }
	if (typeof this._db._batch === 'function') {
	return this._db._batch(this._operations, options, callback)
	}
	process.nextTick(callback)

Notice that _write doesn't receive options.