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

Allow setindex! in zero part of Triangular matrices... #13587

Merged
merged 1 commit into from
Oct 14, 2015

Conversation

mbauman
Copy link
Member

@mbauman mbauman commented Oct 13, 2015

as long as the value is zero. The error message is similar to that of setindex for Diagonal matrices. And similarly for setting the diagonal of UnitTriangular types to one.

Prompted by this SO question. We may want to also think about what a similar triangular matrix is… but that's a bigger question.

@mbauman mbauman force-pushed the mb/triangularsetindex branch from d4a4f81 to 1f50924 Compare October 13, 2015 18:05
@mbauman mbauman force-pushed the mb/triangularsetindex branch from 69a406a to 566acb1 Compare October 13, 2015 18:22
@kshyatt kshyatt added the linear algebra Linear algebra label Oct 13, 2015
andreasnoack added a commit that referenced this pull request Oct 14, 2015
Allow setindex! in zero part of Triangular matrices...
@andreasnoack andreasnoack merged commit d53ea25 into JuliaLang:master Oct 14, 2015
@mbauman mbauman deleted the mb/triangularsetindex branch October 14, 2015 15:09
@mbauman
Copy link
Member Author

mbauman commented Oct 14, 2015

This should be safe to backport.

@tkelman
Copy link
Contributor

tkelman commented Oct 14, 2015

Only if all libraries that rely on this behavior explicitly mark their dependency on the first release version of Julia that has this change backported.

@mbauman
Copy link
Member Author

mbauman commented Oct 14, 2015

Hunh? Yes, this changes the tested interface (error types change, an error becomes a no-op in some situations), but I really would not consider it to be breaking.

@tkelman
Copy link
Contributor

tkelman commented Oct 14, 2015

No, but it could be considered a new feature. User code that formerly errored would now work - so if a package starts relying on the new behavior, it needs to very clearly specify its dependence on the first version of Julia where it started working, otherwise the package would suddenly break upon upgrade for any users who stay on 0.4.0.

@mbauman
Copy link
Member Author

mbauman commented Oct 14, 2015

Gotcha. I was thinking of this more as a bug fix than a feature, but I can see your point. Your call.

@tkelman
Copy link
Contributor

tkelman commented Oct 14, 2015

This is a little of both. I guess the point is more general - even for obvious bug fixes, relying on fixes in backport releases should come with stricter dependency versioning discipline in packages to avoid causing issues for users. At least we now support testing against specific versions in Travis, so packages can test specifically against 0.4.0 (potentially in addition to 0.4-latest) now that it's out.

mbauman added a commit that referenced this pull request Oct 31, 2015
as long as the value is zero

(cherry picked from commit 566acb1)
ref #13587
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
linear algebra Linear algebra
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants