Skip to content

Commit f30411d

Browse files
committed
Update note
1 parent d1db33d commit f30411d

File tree

1 file changed

+1
-1
lines changed
  • lib/node_modules/@stdlib/ndarray/base/unary/src

1 file changed

+1
-1
lines changed

lib/node_modules/@stdlib/ndarray/base/unary/src/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,4 +25,4 @@ limitations under the License.
2525
## Notes
2626

2727
- Each file contains a set of related ndarray functions. The file name matches the ndarray function name suffix for input and output ndarray dtypes.
28-
- The implemented functions which perform conversions are **not** exhaustive and that is intentional. Namely, functions which would perform "unsafe" callback argument and return value conversions are not included (e.g., converting an `int32` to `int16` or `double` to `int32`). If users want to perform "unsafe" conversions, that should be a conscious decision. All the machinery (e.g., macros, typedefs, etc) is available for implementing ndarray functions which perform "unsafe" conversions, but we should not make this overly easy or be proactive in promoting "unsafe" conversion use.
28+
- The implemented functions which perform conversions are **not** exhaustive and that is intentional. Namely, functions which would perform "unsafe" callback argument and return value conversions are not included (e.g., converting `double` to `int32`). If users want to perform "unsafe" conversions, that should be a conscious decision. All the machinery (e.g., macros, typedefs, etc) is available for implementing ndarray functions which perform "unsafe" conversions, but we should not make this overly easy or be proactive in promoting "unsafe" conversion use.

0 commit comments

Comments
 (0)