Repository navigation
Bottom gussets and standing pouches, a certified bound for the shipping objectives, one money
ceiling, and one measure grammar.
Added
deformable_boundary: { kind: 'gusseted_bag', bottom_gusset_depth, orientation }: a bottom
gusset lengthens the girth along the bag, andorientation: 'standing'packs a stand-up pouch
upright.optimality.lower_boundand the gap undershipping_costandlowest_landed_cost;
validatechecks them.examples/checkout.mjsandexamples/fulfilment.mjs.
Changed
- A
rate_tablepriced above 9007199254740991 minor units at its top bracket, surcharge
included, isinvalid_request/above_maximum. The fallback's packingscoreno longer
carries a rounded double past 2^53. Commerce refuses an input integer above 2^53 − 1 with
expected an exact integer, sinceJSON.parsehas already rounded it. - Measures follow the shared grammar:
100.,.5,0x64and100 millimetersare
wrong_type, and"5 /2"is five halves, not 5.hull_verticesholds at most 32 points. - Two equally ranked container types open in code-point order of their ids, not request
order, as in every other engine. Item types in the block solver, policy citations and
validation text follow code-point order, not UTF-16 order. volume_utilizationandsupport_ratioprint six places of the correctly rounded double,
as the other engines do.- The "why unpacked" reason no longer reads the search deadline.
Fixed
qualitycrashed with two payload-limited container types ("Cannot convert a BigInt value
to a number"). This is also in 1.10.0.- A
singleground contact was checked inO(n + kn)per candidate; it is nowO(b)for the
placements on one plane, with the same answers. - A rate table of 125,000 brackets overflowed the stack.
rebalanceWeightdeep-copied the scene for every trial move: 120 items with 4 moves take
0.4 s instead of 21.8 s.- The validator threw on
1e999.