GregWWalters

/* eslint-disable no-bitwise,no-plusplus,no-underscore-dangle */
/* eslint-disable no-func-assign,no-return-assign */

const util = require('../authorization/util');
// TODO: move utils
const MAX_BIT = Math.log2(Number.MAX_SAFE_INTEGER);

/**
 * Get the value of the next bit in the series and increment the next bit
 * value. If the maximum safe bit has already been claimed, it will throw

GregWWalters

In most situations, a reference to a slice in Go is unnecessary. The slice itself contains a pointer to the underlying array, so slices passed as arguments to functions or variables set to slices that are properties of structs can modify the elements of the original slice.

However, if you need to add new elements to the slice, the slice is replaced. By using a reference to the slice, structs and out-of-scope slices can be grown.

For a more complete explanation of why references to slices aren't pointless,

GregWWalters

package testutils

import (
	"encoding/json"
	"errors"
	"fmt"
	"reflect"
)

// MARK: Public Functions