Julia v0.7.0 Release Notes
github.com
Julia v0.7.0 Release Notes
1–10 of 61 posts
Re: Julia v0.7.0 Release Notes
#2Important to note that the 0.7 release is not quite done yet and we are polishing it. So there is no official release candidate yet.
Re: Julia v0.7.0 Release Notes
#3Important to note that the 0.7 release is not quite done yet and we are polishing it. So there is no official release candidate yet.
Is the plan still that 0.7 and 1.0 are the same except for deprecations?
Re: Julia v0.7.0 Release Notes
#4Wow, a bunch of nice features here, named tuples, function argument destructuring... Also a bunch of syntax/parsing cleanups, hopefully for the best.
Re: Julia v0.7.0 Release Notes
#5Important to note that the 0.7 release is not quite done yet and we are polishing it. So there is no official release candidate yet.
I don’t use Julia but those language changes would have me worried that existing code would start behaving differently because of parser changes.
Re: Julia v0.7.0 Release Notes
#6Wow, a bunch of nice features here, named tuples, function argument destructuring... Also a bunch of syntax/parsing cleanups, hopefully for the best.
When I first used named tuples in Swift I thought they'd be so great, no more _1 _2 or whatever. After using them a while, it gets a bit tiring and litters with repeated type info. A type alias for a named tuple would help with that. Any others have similar experiences? Or would they play out differently in Julia?
Re: Julia v0.7.0 Release Notes
#7Wow, a bunch of nice features here, named tuples, function argument destructuring... Also a bunch of syntax/parsing cleanups, hopefully for the best.
When I first used named tuples in Swift I thought they'd be so great, no more _1 _2 or whatever. After using them a while, it gets a bit tiring and litters with repeated type info. A type alias for a named tuple would help with that. Any others have similar experiences? Or would they play out differently in Julia?
Types are first class in Julia.
Re: Julia v0.7.0 Release Notes
#8Wow, a bunch of nice features here, named tuples, function argument destructuring... Also a bunch of syntax/parsing cleanups, hopefully for the best.
When I first used named tuples in Swift I thought they'd be so great, no more _1 _2 or whatever. After using them a while, it gets a bit tiring and litters with repeated type info. A type alias for a named tuple would help with that. Any others have similar experiences? Or would they play out differently in Julia?
Wouldn't that just be a struct?
Re: Julia v0.7.0 Release Notes
#9That heading gives someone who doesn't already know, absolutely no clue what it is or why they should click on it.
Re: Julia v0.7.0 Release Notes
#10Important to note that the 0.7 release is not quite done yet and we are polishing it. So there is no official release candidate yet.
I don’t use Julia but those language changes would have me worried that existing code would start behaving differently because of parser changes.
The forthcoming Julia 0.7 release will provide warning messages for important (and breaking) changes that the community has been clamoring for. I don't think users are "worried" so much as they are planning to review and update their code accordingly. For example, I don't expect my existing 0.5 code to work without substantial revisions. This is the last window to improve the language proper before the 1.0 release, after which users like me will expect stability.