Skip to content

Broadcasting fix for Julia 1.5 #370

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

Closed

Conversation

mbauman
Copy link

@mbauman mbauman commented Jun 1, 2020

Hello! Julia 1.5 very minimally changes what is required of an object to support its use on the left-hand-side of a .= assignment. This adds the one extra overload that is needed to get tests passing on 1.5 and adds version 1.5 to the CI test matrix.

That said, I'm not entirely sure you want to use.= for this purpose — it's a little strange that WeightedNorm only supports appearing on the left hand side of a broadcast expression and not on the right. I'd be happy to help you make WeightedNorm work more fully in broadcast if that makes sense for your uses.

See JuliaLang/julia#36105 for the core language discussion and more details if you're interested.

@mbauman
Copy link
Author

mbauman commented Jun 1, 2020

Ah shucks, we don't have GitHub actions set up to use the 1.5 beta yet. That was a bit of a shot in the dark.

@saschatimme
Copy link
Member

Hey Matt,

I already backported a patch which should fix the PkgEval error here : #367
(And also released 1.4.3, the current master is in preparing 2.0)

@saschatimme
Copy link
Member

This actually doesn't fix the error, but the tests don't hit it anymore, and since this is only used internally where it is never called this way.

@saschatimme saschatimme closed this Jun 1, 2020
@mbauman mbauman deleted the mb/onepointfive branch June 1, 2020 18:19
@mbauman
Copy link
Author

mbauman commented Jun 1, 2020

Ah, nice! Thanks for the update, and glad you were able to work around it!

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