-
-
Notifications
You must be signed in to change notification settings - Fork 450
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
blog post: Julia 1.6 Highlights #1135
Conversation
Once the build has completed, you can preview your PR at this URL: https://julialang.netlify.app/previews/PR1135/ in ~15 minutes |
There are several sections here that people need to write and someone needs to add a little conclusion. I will not be around to work on this, so others should feel free to push and pull their changes. Consider this a public branch: don't force push at the risk of overwriting someone else's changes. Once it's all ready, fix up the date and squash merge to publish. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formatting fixes
Co-authored-by: Ian Butterworth <[email protected]>
Co-authored-by: Ian Butterworth <[email protected]>
Co-authored-by: Mosè Giordano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Co-authored-by: Tim Holy <[email protected]>
Co-authored-by: Ian Butterworth <[email protected]>
@staticfloat: I would avoid making it sounds like binary dependencies have been especially problematic for Julia. Rather, this is a generally hard problem and today Julia has a uniquely fast, portable and reliable solution which just got even faster. |
blog/2021/02/julia-1.6-highlights.md
Outdated
|
||
_Jameson Nash and Jeff Bezanson_ | ||
|
||
In addition to making our library code more compiler-friendly, we continue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this is just my lack of understanding, but what is library code vs regular code? Perhaps worth mentioning?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All code is library code
blog/2021/02/julia-1.6-highlights.md
Outdated
breakthroughs, but we do have some modest improvements due to work on the | ||
method table data structure. | ||
|
||
Method specificity is a partial order, and prior to 1.6 we stored methods in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Method specificity is a partial order, and prior to 1.6 we stored methods in | |
Method specificity is stored in partial order, prior to 1.6, we stored methods in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we keep the same wording here, perhaps adding a link to: https://en.wikipedia.org/wiki/Partially_ordered_set would help anyone scratching their head as I was
blog/2021/02/julia-1.6-highlights.md
Outdated
downloading was done by some external process—whichever one of `curl`, `wget`, | ||
`fetch` or `PowerShell` happened to be available on your system. The fact that | ||
this frankendownload feature worked at all was something of a miracle, that only | ||
worked due to much fussy command-line-option finessing of over the years. And |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
worked due to much fussy command-line-option finessing of over the years. And | |
worked due to much fussy command-line-option finessing over the years. And, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
of
seems fine. The comma, perhaps?
@StefanKarpinski I did a grammar/spelling/readability check. Feel free to ignore my suggestions. Who is writing up the conclusion? There is so much great stuff here, nice work everyone! |
@logankilpatrick I think you're welcome to push edits directly. I happened to independently make some of those same fixes when reading through, but more polish is better |
I added a section about the new stacktrace formatting (image used from https://www.oxinabox.net/2021/02/13/Julia-1.6-what-has-changed-since-1.0.html#clearer-stacktraces with permission from @oxinabox) and changed the conclusion to just be a rehash of the one we used for 1.5. |
Wordsmithing to make it focus on confidence in release.
Co-authored-by: Rafael Fourquet <[email protected]>
No description provided.