-
-
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
replace ambiguous scale! methods #24276
Comments
Moreover we should consider whether |
The fundamental question here is exactly the same as in #16772 so let's keep the general discussion in that issue. Whatever we decide and as you point out, it makes sense to deprecate these in favor of mutating multiplication. The methods are already defined in Lines 233 to 238 in 0385a60
|
Yes, apart from the additional question of whether |
Triage settled on deprecating |
That implies that mul1! and mul2! should be exported, since |
Is anybody working on this, or should I take a crack at it? |
Let me do it. |
Discussion in #16772 revealed some dubious
scale!
methods. For example (#16772 (comment)), determining what either ofdoes requires reading the associated code. And as
@Keno
suggests, expressing these operations as e.g.A*Diagonal(B)
might be better. Best!The text was updated successfully, but these errors were encountered: