Skip to content
This repository was archived by the owner on Jul 10, 2025. It is now read-only.

RFC: Making dtype promotion semantics in Tensorflow more consistent - #431

Open
JW1992 wants to merge 20 commits into
tensorflow:masterfrom
JW1992:pull-request-promotion-semantics
Open

RFC: Making dtype promotion semantics in Tensorflow more consistent#431
JW1992 wants to merge 20 commits into
tensorflow:masterfrom
JW1992:pull-request-promotion-semantics

Conversation

@JW1992

Copy link
Copy Markdown

This RFC will be open for comment until Friday, November 4th, 2022.
cc @wangpengmit

Making dtype promotion semantics in Tensorflow more consistent

Status(Proposed)
Author(s)Jiawei Xia (Google), Antonio Sanchez (Google)
SponsorPeng Wang (Google)
Updated2022-10-18

Objective

Currently TF has no consistent, well-defined type promotion rules. This document proposes a well-defined, consistent and clear dtype promotion rule for TF. The introduced changes make TF APIs more similar to NumPy, with some differences that emphasize TF’s applications in machine learning. This should make dtype promotions in TF much more consistent and predictable. Specifically the doc discusses the preferred dtype promotion semantics/behaviors of Tensorflow (TF) and Tensorflow-numpy (TF-numpy) in the binary ops including add, sub, mul, div, pow and mod.

@JW1992
JW1992 marked this pull request as ready for review October 19, 2022 00:32
@JW1992JW1992 changed the title Pull request promotion semanticsRFC: Making dtype promotion semantics in Tensorflow more consistentOct 19, 2022
Comment threadrfcs/20221018-promotion-semantics.md Outdated
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@JW1992@wangpengmit