-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add news post about Erlang/OTP 28, release candidate 1 #164
Conversation
✅ Deploy Preview for erlang-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
lgtm. Here is the generated new item if you want to read that: https://deploy-preview-164--erlang-org.netlify.app/news/174
b36595f
to
e807c25
Compare
_news/174.md
Outdated
[`sets`](https://www.erlang.org/doc/apps/stdlib/sets.html) | ||
will now be represented as maps. | ||
|
||
- Module [`re`](https://www.erlang.org/doc/apps/stdlib/re.html) has |
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.
Should this link (and others) point to the new documentation for rc1?
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.
Yes, ideally, but I am not sure where this documentation will be. Maybe it's easier to adjust the links when the release has been built? Any thoughts, @proxyles or @garazdawi?
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.
As the rc1 docs will have the version number of the app in them, it is easier to just update when the docs are published.
We should let our users know that, in the Github Release page, we have included a source Software Bill of Materials (source SBOM) and would like feedback on it. But this is not included in Erlang/OTP per se, just in the Release page and generated by a Github Action |
@bjorng It is tricky to add this as a highlight in the OTP ticket, because the source SBOM is not in the Erlang/OTP repo, but an addition outside the OTP repo. |
@kikofernandez I've pushed a fixup commit with a new paragraph about SBOMs. I included a link to an article I found that explains the concept of SBOMs. |
@kikofernandez The link I found is on Gitlab and contains some irrelevant material (how Gitlab helps making SBOMs). Feel free to suggest another link. |
@garazdawi There is one broken link:
This doesn't seem to be caused by my PR, so it seems to be broken already in |
8b83ae1
to
0ae2895
Compare
- Some BIFs with side-effects (such as `binary_to_atom/1`) are | ||
optimized in `try` ... `catch` in the same way as guard BIFs in | ||
order to gain performance. | ||
|
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.
Suggested addition:
- Improved performance of the compiler's alias analysis pass to roughly halve the time required for the analysis. The improved performance allows improvements in the analysis to handle chains of extracts where it previously it only handled the innermost embed+extract pair and conservatively classified longer chains as producing an aliased value. (#8695)
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.
I added an edited version of your suggestion, which is lighter on technical details and also pointing what the benefit is for the user:
- The compiler’s alias analysis pass is now both faster and less conservative, allowing optimizations of records and binary construction to be applied in more cases.
I've created a reminder for myself to add a release note for RC2 about compiler optimizations.
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.
I like what you did with my blurb!
0ae2895
to
9517a54
Compare
doc changes
No description provided.