If we had such a policy, and a PR hit that time window without meeting the
criteria, I'd expect that it would be closed without being merged.
In other words, such a policy would cause open unmerged PRs to be *closed*
- but in no way could, or should, such a policy accelerate *merging*.
The only
Hi,
This already has a Stage 0 proposal here:
https://github.com/tc39/proposal-bind-operator.
You can find all proposals at https://github.com/tc39/proposals in
(currently) three categories: That page itself, which lists proposals for
Stages 1, 2, and 3; and the linked lists of Stage 0
Sometimes, you need to pass a callback as a parameter of a function.
Sometimes, you would like to pass in a method as the said parameter but you may encounter the common issue that the this keyword is not bound to the correct context anymore ; therefore you need to bind the correct context.
A month ago I opened a github issue (
https://github.com/tc39/ecma262/issues/1061) in which I asked whether or
not TC39 should have a policy WRT the time frame in which a PR should be
merged. I mentioned that there was currently an open PR (
https://github.com/tc39/ecma262/pull/666) which had
4 matches
Mail list logo