Ali Mohammad Pur

> ignore the fractional coordinate part shouldn't we figure out why having them leads to gaps in the first place?

You _could_ do this: ```c++ Optional moved_to_array; { NoAllocationGuard guard; moved_to_array.emplace(move(moved_from_array)); } ``` Also, remind me why the FixedArray destructor needs to allocate...?

> It frees which might be also blocked by the guard it's a No**Allocation**Guard, doesn't sounds like something that would be blocking free :thinking:

First commit lgtm, but as I said before, I don't like the entirely separate expression type, it's a hack on top of a hack (specialised typecheck for format) meant to...

Let's have the feature, we can simplify later, no need to block.

You can look at how the various `DOMException`s are currently implemented, these basically follow the same concept. looks like they're just `PlatformObject`s now:

There's an option for that (which is probably not exposed in the GUI), it can either read zeros or wrap around the image. There's no real universal solution to this...

Not really? `maxIf(_ => false)` _is_ valid, the function's signature is ```js function maxIf(condition, ...cells) ``` and calling `maxIf(any)` is equivalent to `Math.max()`, which I believe will yield `-Infinity`. Now...

Tracking continuation in #1242.

Implemented in dc4e06920f30dc9b27f54bca04f5aa4b9d6cc867.