Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 20 commits into
base: master
Choose a base branch
from

Conversation

JW1992
Copy link

@JW1992 JW1992 commented Oct 19, 2022

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)
Sponsor Peng Wang (Google)
Updated 2022-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
@JW1992 JW1992 changed the title Pull request promotion semantics RFC: Making dtype promotion semantics in Tensorflow more consistent Oct 19, 2022
rfcs/20221018-promotion-semantics.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants