Update dtypes

kgryte · kgryte · commit f7ff9eae9fc8 · 2021-03-18T21:23:46.000-07:00
diff --git a/lib/node_modules/@stdlib/ndarray/dtypes/include/stdlib/ndarray/dtypes.h b/lib/node_modules/@stdlib/ndarray/dtypes/include/stdlib/ndarray/dtypes.h
@@ -30,10 +30,13 @@ extern "C" {
 * Enumeration of underlying ndarray data types.
 */
 enum STDLIB_NDARRAY_DTYPE {
-	// STDLIB_NDARRAY_BOOL = 0, // TODO: uncomment once supported
+	// Boolean data types:
+	STDLIB_NDARRAY_BOOL = 0,
 
-	STDLIB_NDARRAY_INT8 = 0, // NOTE: remove explicitly setting value once `bool` supported
+	// Integer data types:
+	STDLIB_NDARRAY_INT8,
 	STDLIB_NDARRAY_UINT8,
+	STDLIB_NDARRAY_UINT8C,
 	STDLIB_NDARRAY_INT16,
 	STDLIB_NDARRAY_UINT16,
 	STDLIB_NDARRAY_INT32,
@@ -45,11 +48,22 @@ enum STDLIB_NDARRAY_DTYPE {
 	// STDLIB_NDARRAY_INT256,
 	// STDLIB_NDARRAY_UINT256,
 
+	// Floating-point data types:
 	// STDLIB_NDARRAY_FLOAT16, // TODO: uncomment once supported
 	STDLIB_NDARRAY_FLOAT32,
 	STDLIB_NDARRAY_FLOAT64,
 	// STDLIB_NDARRAY_FLOAT128 // TODO: uncomment once supported
 
+	// Complex floating-point number data types:
+	// STDLIB_NDARRAY_COMPLEX64, // TODO: uncomment once supported
+	// STDLIB_NDARRAY_COMPLEX128,
+
+	// Define a data type for "binary" data (i.e., data stored in a Node.js `Buffer` object):
+	STDLIB_NDARRAY_BINARY,
+
+	// Define a data type for "generic" JavaScript values (objects):
+	STDLIB_NDARRAY_GENERIC,
+
 	// "Compute" the number of data types (this works because of how `enum` works: the value is automatically set to the last enumerated type plus 1):
 	STDLIB_NDARRAY_NDTYPES,
 
diff --git a/lib/node_modules/@stdlib/ndarray/dtypes/lib/enum.js b/lib/node_modules/@stdlib/ndarray/dtypes/lib/enum.js
@@ -39,37 +39,42 @@
 function enumerated() {
 	// NOTE: the following should match the C `dtypes.h` enumeration!!!!
 	return {
-		// 'bool': 0, // uncomment once supported
+		// Boolean data types:
+		'bool': 0,
 
-		'int8': 0,
-		'uint8': 1,
-		'int16': 2,
-		'uint16': 3,
-		'int32': 4,
-		'uint32': 5,
-		'int64': 6,
-		'uint64': 7,
-		// 'int128': 9, // uncomment once supported
-		// 'uint128': 10, // uncomment once supported
-		// 'int256': 11, // uncomment once supported
-		// 'uint256': 12, // uncomment once supported
+		// Integer data types:
+		'int8': 1,
+		'uint8': 2,
+		'uint8c': 3,
+		'int16': 4,
+		'uint16': 5,
+		'int32': 6,
+		'uint32': 7,
+		'int64': 8,
+		'uint64': 9,
+		// 'int128': 10, // uncomment once supported
+		// 'uint128': 11,
+		// 'int256': 12,
+		// 'uint256': 13,
 
-		// 'float16': 13, // uncomment once supported
-		'float32': 8,
-		'float64': 9,
-		// 'float128': 16, // uncomment once supported
+		// Floating-point data types:
+		// 'float16': 14,
+		'float32': 10,
+		'float64': 11,
+		// 'float128': 17, // uncomment once supported
 
-		// Define a signaling value which is guaranteed not to be a valid type enumeration value:
-		'notype': 11,
+		// Complex floating-point number data types:
+		// 'complex64': 18, // uncomment once supported
+		// 'complex128': 19,
 
-		// The following is a special dtype, which is, in more recent Node.js versions, effectively equivalent to `uint8` when calling into C; however, in older Node.js versions, the `Buffer` object was not based on the `Uint8Array` typed array. Here, we treat "binary" as an alias for `uint8`.
-		'binary': 1,
+		// Data type for "binary" data (i.e., data stored in a Node.js `Buffer` object):
+		'binary': 12,
 
-		// The following is a special dtype which is only applicable in JavaScript, not in C. Here, we treat "uint8c" as an alias for `uint8`.
-		'uint8c': 1,
+		// Data type for "generic" JavaScript values (objects):
+		'generic': 13,
 
-		// The following corresponds to a "generic" JavaScript `Array` instance. This has no equivalent native C type.
-		'generic': 11,
+		// Define a signaling value which is guaranteed not to be a valid type enumeration value:
+		'notype': 15,
 
 		// Indicate the start of user defined type numbers (leaving room for type growth above):
 		'userdefined_type': 256
