How about extending debugger statement? Eg. debugger.assert.
On Mon, 14 Jan 2019, 12:39 Michael Haufe <[email protected] wrote: > console.assert is not standardized at this point, nor is it part of the > language. Additionally, the semantics are inappropriate for the required > use cases. > > To requote the relevant part from the linked thread: > > 1. AssertionError <: Error > 2. assert(x === 12); // throws an AssertionError with a default error > message > 3. assert(x === 12, "twelve, supposedly") // throws an AssertionError with > the given error message > > console.assert does not throw and its intent is not the same. The assert > I'm referring to is related to Code Contracts. Therefore your reference is > seemingly orthogonal. > > /Michael > > On Sun, Jan 13, 2019, 12:49 Cyril Auburtin <[email protected] > wrote: > >> There's `console.assert` >> >> also check >> https://github.com/michaelficarra/proposal-first-class-protocols/issues/27#issuecomment-386975099 >> >> >> On Sun, Dec 16, 2018 at 10:01 PM Michael Haufe <[email protected]> >> wrote: >> >>> Seven years ago there was discussion around standardizing "assert". Has >>> there been any movement on this since then? >>> >>> https://esdiscuss.org/topic/native-assertion-module >>> >>> >>> _______________________________________________ >>> es-discuss mailing list >>> [email protected] >>> https://mail.mozilla.org/listinfo/es-discuss >>> >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
