The Rules Behing Rust Functions

Posted4 months agoActive4 months ago

gidellav

53 points

15 comments

blog.cuongle.devTechstory

calmpositive

Debate

20/100

Rust Programming LanguageFunction SyntaxCompiler Design

Key topics

Rust Programming Language

Function Syntax

Compiler Design

The article explores the rules behind Rust functions, sparking a discussion on code presentation and comparisons with other languages.

Snapshot generated from the HN discussion

Discussion Activity

Moderate engagement

First comment

Peak period

84-96h

Avg / period

3.5

Comment distribution7 data points

Loading chart...

Based on 7 loaded comments

Key moments

01Story posted
Sep 10, 2025 at 4:58 PM EDT
4 months ago
Step 01
02First comment
Sep 14, 2025 at 9:10 AM EDT
4d after posting
Step 02
03Peak activity
6 comments in 84-96h
Hottest window of the conversation
Step 03
04Latest activity
Sep 19, 2025 at 12:18 AM EDT
4 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (15 comments)

Showing 7 comments of 15

cratermoon

4 months ago

2 replies

To the author of this blog post: please write the code examples as syntax-colored text, and definitely not as images. I'd love to copy the code and paste it into the Rust playground or godbolt, so I can see exactly what the compiler does and how the code behaves. I can't do that with screenshots of code.

CamJN

4 months ago

2 replies

You can on Apple’s OSs, and some googling suggests you can do it on windows too if you save the image and open in the image viewer. Therefore I’d be surprised if you couldn’t get it working on various linux distros too...

Klonoar

4 months ago

You have to understand how ridiculous this answer sounds.

This is a technical forum. There is an expectation of how things are shared. Images and relying on built in OCR is not anywhere in line with that expectation.

Jaxan

4 months ago

Still it would be nice if the author used the right format for the job.

cuongleqq

4 months ago

Hi, author here.

I didn't know my post was submitted here. So sorry for the late answer.

The problem with code on substack is that they don't have syntax highlight which make reading the code a pain :( Let me see how to improve it in the next posts.

Thank you for reading!

kazinator

4 months ago

You'd never have written "behing" if your keyboard's firmware, all the drivers, OS and the GUI and input control were written in Rust!

fulafel

4 months ago

Would be interesting to see a comparison with GCC's C closures[1].

[1] https://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html

8 more comments available on Hacker News

View full discussion on Hacker News

ID: 45203601Type: storyLast synced: 11/20/2025, 3:41:08 PM

Want the full context?