Meeting Room Booking System
Interval conflicts and atomic room allocation
Ownership and transitions
Half-open intervals overlap when a.start<b.end and b.start<a.end; touching endpoints are compatible. Multi-room allocation plans all candidates before committing any, so an insufficient-room failure reserves nothing. A successful booking ID stays reserved after cancellation, while failed IDs may be retried. Capacity/ID sorting makes allocation deterministic. Scan-based selection costs O(rooms*bookings) plus candidate sorting.
JavaScript boundaries
Use native classes with per-instance state and plain object/array snapshots. Object assignment shares a reference; copy retained inputs and every outward mutable container, including nested arrays. null means absence. Map handles arbitrary string keys safely, including "__proto__"; do not confuse a missing key with zero or an empty string. Domain validation uses RangeError. Numeric inputs must satisfy Number.isSafeInteger, so booleans, fractions, infinities, and NaN are invalid where an integer is required. All documented aggregate results and timestamp-plus-duration sums fit the safe-integer range. Strings use exact case-sensitive equality; lexical order compares JavaScript UTF-16 code units. Calls are serialized and synchronous.
const internal = ["initial"];
const snapshot = [...internal];
snapshot.length = 0;
console.assert(internal.length === 1);A detached snapshot protects ownership; the service still has to validate and commit a coherent transition.
Put it into practice
Implement the exercise in a full-screen workspace, then run its tests.