Skip to content

Commit 436c97f

Browse files
authored
Update guidance for output array dtype inference in full_like (#274)
* Update guidance on full-like dtype inferrence * Update copy
1 parent c587656 commit 436c97f

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

spec/API_specification/creation_functions.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -239,10 +239,14 @@ Returns a new array filled with `fill_value` and having the same `shape` as an i
239239
240240
- **dtype**: _Optional\[ <dtype> ]_
241241
242-
- output array data type. If `dtype` is `None`, the output array data type must be inferred from `fill_value` (see {ref}`function-full`). Default: `None`.
242+
- output array data type. If `dtype` is `None`, the output array data type must be inferred from `x`. Default: `None`.
243243
244244
```{note}
245-
If `dtype` is `None` and the `fill_value` exceeds the precision of the resolved default output array data type, behavior is left unspecified and, thus, implementation-defined.
245+
If `dtype` is `None` and the `fill_value` exceeds the precision of the resolved output array data type, behavior is unspecified and, thus, implementation-defined.
246+
```
247+
248+
```{note}
249+
If `dtype` is `None` and the `fill_value` has a data type (`int` or `float`) which is not of the same data type kind as the resolved output array data type (see {ref}`type-promotion`), behavior is unspecified and, thus, implementation-defined.
246250
```
247251
248252
- **device**: _Optional\[ <device> ]_

0 commit comments

Comments
 (0)