-
Notifications
You must be signed in to change notification settings - Fork 292
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 blog post about Google Summer of Code 2024 project results #1419
Conversation
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.
The cargo-semver-checks part looks quite good, thank you for writing it up!
Minor polish suggestions: one readability tweak + a few words of extra context for why the project is meaningful (not just what it did).
The draft was bootstrapped by David Lattimore, the mentor of the project.
I drafted a description of the Cranelift register allocator project (https://github.com/rust-lang/blog.rust-lang.org/blob/b9efc93c907687ee649b5c44cb92c799a2f9157b/posts/2024-11-01-gsoc-2024-results.md#implementation-of-a-faster-register-allocator-for-cranelift). @Amanieu @cfallin Could you please check it out and review it? Thank you! |
@Kobzol the writeup about the regalloc work looks great -- thanks so much for writing that! |
I drafted a description of the .NET backend project (https://github.com/rust-lang/blog.rust-lang.org/blob/5c123051346736a6bdf6ae2ea8ee3dcad502b76e/posts/2024-11-01-gsoc-2024-results.md#rust-to-net-compiler---add-support-for-compiling--running-cargo-tests). @jackh726 @FractalFir Could you please check it out and review it? Thank you! |
From a first glance at this description, I'd say it is mostly OK. There are some minor things I would suggest adjusting or am a bit unsure about. The "C_MODE" part of my project is still an experiment and is less mature than the .NET part of it. Right now, the "C_MODE" is almost capable of building the Another thing I would suggest needs some changes is the percentage of passing Also, I don't know if that is worth mentioning, but those are the I am also wondering about one other thing: almost all other participants seem to use their real names. Do you think maybe my real one should be included too? My real name (Michał Kostrubiec) has been publicly available for some time now, and the main reason I use my username is the fact that it is what I am known as. Maybe something like' Fractal Fir aka Michał Kostrubiec' would look better/more consistent? I don't know what is the standard practice in open source(handles vs names), but anything(name, handle, both) is fine by me. Besides those very minor nitpicks, this looks more than fine :)! |
@ytmimi @ding-young I created a draft of the rustfmt project description, but I'm not actually sure what was the outcome 😅 Could you please take a look? https://github.com/rust-lang/blog.rust-lang.org/blob/a7cac06c05cdb4f94939567f578af84d396757bb/posts/2024-11-01-gsoc-2024-results.md#rewriting-the-rewrite-trait |
I went through the blog post again and didn't find any issues (just made some cosmetic changes). This should now be ready for a merge anytime. Whoever can approve, please do :) |
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.
This is great, I hadn't followed the GSoC projects closely and it sound like this program was a really big success for us.
This blog post describes the results of the 2024 Rust (Foundation/Project) GSoC projects. It is a follow-up to https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html and https://blog.rust-lang.org/2024/02/21/Rust-participates-in-GSoC-2024.html.
This is now ready for a final review. I plan to publish it on Thursday 7th November 2024.
Rendered