Keith Cirkel

So to clarify - if the committee decides that `array[:-1]` could be a viable option, then `array[:-N]` would absolutely be up for discussion/proposal.

Closing this. The Readme has been updated to reflect the current state of this proposal which features `Array.prototype.end` getter/setter.

> you'd still have to resort to arr[arr.length-1] = foo; I've updated the proposal to be a getter/setter. So this is no longer an issue... however... > we could also...

I'm not opposed to the idea, on the surface it seems good. There are two concerns with this though: 1. Web compat; does there exist an in-the-wild assignment of `Array.prototype.get`/`Array.prototype.set`?...

PRs always welcome 👍

For a project I'm working on we use rollup, and we memoize all calls to rollup - as well as every call to our transform plugins (mostly babel), and the...

We were unable to get Rollup's existing cache to persist to disk, so we rolled our own which works over the top of rollup. For our own cache system -...

I would generally give a 👎 for `node_modules/.cache/rollup` as its likely that most CIs will throw away `node_modules` for each build. Some libraries use npm's cache folder (typically `~/.npm`), which...

Hey @ExploreMqt thanks for the pr You can use `#{act}` instead, and then pass it as another argument, which is more the chai convention. [An example](https://github.com/chaijs/chai/blob/master/lib/chai/core/assertions.js#L523)

Sorry to be a pain @ExploreMqt - could you also add some tests for this? It'd be nice to have some tests to back up the code is doing what...