Skip to content

add blog post "Stabilizing naked functions" #1650

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add blog post "Stabilizing naked functions" #1650

wants to merge 1 commit into from
+147 −0

Conversation

folkertdev
Copy link
Contributor

@folkertdev folkertdev commented Jun 23, 2025 •
edited by rustbot
Loading

Providing an introduction to naked functions, some background on the 10-year journey to stabilization, and some future features related to inline assembly.

cc @tgross35 @joshtriplett

  • I'm not sure what my mandate is exactly here, so I just filled in something
  • I'm also not sure what is good in terms of scheduling (but probably not too long after the release?)

Rendered

@tgross35 tgross35 mentioned this pull request Jun 24, 2025
Closed
@folkertdev folkertdev force-pushed the stabilize-naked-functions branch from d01096f to caea311 Compare June 24, 2025 08:32
@folkertdev folkertdev changed the title add blog post "Stabilizing naked functions" [inside-rust] add blog post "Stabilizing naked functions" Jun 24, 2025
@pthariensflame pthariensflame mentioned this pull request Jun 25, 2025
Merged
@jieyouxu
Copy link
Member

Hi, noticed this while reviewing the 1.88 relnotes (#1651 (comment)).

I feel like this should be a public Blog Post, because this is about the stabilized user-facing language feature, especially about "well, why do we need this language feature in the first place"?

Sure, it has some tidbits on the implementation details on how we got to stabilized naked functions, and some possible future directions, but I think that might also be interesting for the community at large :)

@folkertdev folkertdev force-pushed the stabilize-naked-functions branch from caea311 to 1dbdd38 Compare June 25, 2025 14:31
@folkertdev folkertdev changed the title [inside-rust] add blog post "Stabilizing naked functions" add blog post "Stabilizing naked functions" Jun 25, 2025
@folkertdev
Copy link
Contributor Author

Sure, I've adjusted it, and made some further small tweaks/typo fixes.

@folkertdev folkertdev force-pushed the stabilize-naked-functions branch 2 times, most recently from 63ddac4 to e323c5b Compare June 26, 2025 20:09
@joshtriplett
Copy link
Member

This looks good to me. 👍 🚢

@folkertdev folkertdev force-pushed the stabilize-naked-functions branch from e323c5b to 6e8b140 Compare June 30, 2025 12:07
@folkertdev
Copy link
Contributor Author

Made some final tweaks

  • updated the date to today
  • made all headerstart with an uppercase letter
  • clarify the name a bit
  • link to the 1.88.0 release blog post

With that, I think this is ready, but it looks like it needs a re-approve?

tgross35
tgross35 reviewed Jun 30, 2025
View reviewed changes
Copy link
Contributor

@tgross35 tgross35 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A handful of optional comments from one final read through, but overall this looks pretty great!

@folkertdev folkertdev force-pushed the stabilize-naked-functions branch from 6e8b140 to 16b4124 Compare June 30, 2025 14:01
tgross35
tgross35 approved these changes Jun 30, 2025
View reviewed changes
Copy link
Contributor

@tgross35 tgross35 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me as well!

@folkertdev folkertdev force-pushed the stabilize-naked-functions branch from 16b4124 to b4a94c2 Compare July 1, 2025 09:38
@folkertdev
Copy link
Contributor Author

I updated the date. I'm not sure how signing off on blog posts works exactly, how does the decision to actually merge/post get made?

@tgross35
Copy link
Contributor

tgross35 commented Jul 1, 2025

Since Josh approved it I think it just needs somebody with permissions to merge. @traviscross maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@joshtriplett joshtriplett joshtriplett approved these changes

@tgross35 tgross35 tgross35 approved these changes

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@folkertdev @jieyouxu @joshtriplett @tgross35