Repository navigation
Packvium 1.8.0
Results now say how far they can be from the best possible answer, optimal means a proof,
and a mistyped flag is refused instead of guessed.
Added
optimality.lower_boundand the gap under thedefaultandlowest_costobjectives;
Packvium\Validation\validatechecks them.- The
src-legacy/generator (scripts/build_php74.py,tools/php-compat/), which
rebuilds the shipped tree byte for byte from a tag.
Changed
- Attaining the bound, not search exhaustion, sets
optimal(proven_optimal). - An effort budget names a stop: a run that ends on exactly its budget is
complete, and
time_limit_msis no longer split across starts. Checktermination.any_start_truncated. ArrayCodec::packrefuses a non-booleankeep_upright,stackable,must_be_on_floor
orrequire_placement_coordinatesaswrong_type;"no"packed as stackable. The
constructors are unchanged: withoutstrict_types, PHP still converts the value.
Packvium\Validation\validatethrowsMalformedResult(contract) for such a request, and
readsnullas the default.- Solves 2-15% faster, the loading-order check about twice as fast, identical answers.
- The JSON path avoids a redundant object check:
ArrayCodec::packretains request
admission and model checks, and compiles fewer files. Direct measurements on the macOS
host removed about 0.5 ms of compilation/checking work on the unpackable request; the
additional end-to-end gain was within the A/A noise. This is wall time, not CPU time. - Placement under axle limits is about 2.5-3x faster, unloading orders about 5% faster;
answers are identical.
Fixed
homogeneous_blocksnamed alone packs underfastandbalanced, and a node-limit
stop is no longer reported astime_limit.- A bound past the declared ceiling no longer throws
BoundOverflowException. validatereadsunits: nullandunits.length: nullas millimetres, as the engines do,
and refuses aunitsthat is not an object, or an unknownunits.length, as acontract
MalformedResultnaming the field.units.weightis not a field and is ignored: put the unit
on each weight.