import { deepEquality } from '@santi100/equal-lib'; function indexOf(arr: any[], item: any) { for (const idx in arr) { if (deepEquality(arr[idx], item)) return arr[idx]; } return -1; } export class AssertionError<E = unknown, A = unknown> extends Error implements AssertOptionalParams<E, A> { /** * Expected value for the assertion. */ readonly expected: E; /** * Received value for the assertion. */
I intend to stop using null in my code, in favor of undefined. There are many reasons for doing so. Feedback wanted Tweet: https://twitter.com/sindresorhus/status/1114894287387258886 Background http://2ality.com/2013/05/history-undefined.html Reasons From experience, most developers use null and undefined inconsistently and interchangeably, and few know when to use which. Supporting both null and
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く