-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
type computation in broadcast is worse than in map #16164
Comments
I believe this not really a type inference issue but a type computation issue due to a missing piece in the promote_op machinery. |
I think |
Another instance of the same problem: |
stevengj
changed the title
type inference in broadcast is worse than in map
type computation in broadcast is worse than in map
May 4, 2016
timholy
pushed a commit
that referenced
this issue
May 4, 2016
timholy
added a commit
that referenced
this issue
May 4, 2016
Add a promote_op method to solve #16164.
This was referenced May 5, 2016
Duplicate of #4883. (Yes, I duplicated my own issue. Sigh.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With current 0.5 master:
We presumably want to return a
Float32
array in both cases?cc: @ViralBShah: this affects the case you asked about in #8450, since my
f.(x...)
implementation in #15032 is equivalent tobroadcast
.The text was updated successfully, but these errors were encountered: