Skip to content

Conversation

@ChrisRackauckas
Copy link
Member

It always defines an Array which can fail on the GPU. This forces it to be the right type. One could also use adapt here, but since the element type promotion would have to occur anyways in the subsequent broadcast it seems you might as well convert all at once.

It always defines an `Array` which can fail on the GPU. This forces it to be the right type. One could also use `adapt` here, but since the element type promotion would have to occur anyways in the subsequent broadcast it seems you might as well convert all at once.
@codecov
Copy link

codecov bot commented Jun 11, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.24 🎉

Comparison is base (a25656d) 87.08% compared to head (af7a10d) 87.32%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #105      +/-   ##
==========================================
+ Coverage   87.08%   87.32%   +0.24%     
==========================================
  Files           3        3              
  Lines         209      213       +4     
==========================================
+ Hits          182      186       +4     
  Misses         27       27              
Impacted Files Coverage Δ
ext/AbstractFFTsChainRulesCoreExt.jl 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@stevengj
Copy link
Member

stevengj commented Jun 12, 2023

LGTM, aside from CI failures. (Unrelated?)

@ChrisRackauckas
Copy link
Member Author

Looks like those are inference errors from v1.9 that inferred well on v1.8. But those tests that are failing don't call AD so it should be unrelated.

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.

3 participants