(I don't know how hard it is to push a different object to an existing SHA on GitHub—I'm guessing that you probably have to remove all references to the original object at that SHA?)
834 karma · joined February 20, 2014
let lock = Promise.resolve()
return (...args) => {
const result = lock.then(() => f(...args))
lock = result.catch(() => {})
return result.then(v => v)
}
}(I don't know how hard it is to push a different object to an existing SHA on GitHub—I'm guessing that you probably have to remove all references to the original object at that SHA?)
[1]: https://en.wikipedia.org/wiki/Employee_Stock_Ownership_Plan
This is a particularly sharp example though.
In colloquial use, "incident" has recently taken on a negative connotation because people don't generally use it except to refer to situations they would rather not elaborate upon. But in the slightly-formal language of newspaper writing it is frequently used to refer to the event that the article is talking about without repeating themselves. In this context it is neutral and has no negative connotation.
Most lenses are "distortion corrected" because they assume they will be displayed on a flat surface. A little explanation for those not familiar: When you take a picture of a brick wall with your camera parallel to the wall, notice that the bricks on the edge of the photo are the same size as the ones in the center, even though the edge bricks are further away from the camera. This means more pixels are allocated per degree of view near the edge of the field-of-view than at the center.
An "uncorrected" lens is basically what we would call a "fish-eye" lens. Here (ideally) the same number of pixels are in a one-degree circle in the center of the field-of-view as are in a one-degree circle near the edge.
I don't think they would crow about just using an "uncorrected" lens either, so I'm going to guess that this is a "reverse-corrected" lens system where a one-degree circle in the center gets more pixels than it would at the edge. This would be the obvious approach if they want a good center crop but want to capture all the periphery as well.
https://www.motorauthority.com/news/1135084_us-finally-allow...
The only exception I can think of is proper tail calls, which Google explicitly removed and I don't know if Mozilla ever tried to implement: https://compat-table.github.io/compat-table/es6/#test-proper... https://chromestatus.com/feature/5516876633341952