2024/08-monthly: Add link to engineering document

Author: CohenArthur

2024/2024-08-monthly-report.org

@@ -12,7 +12,7 @@ This month saw really good progress in terms of the number of merged PRs, issues
 
 In fact, we are currently working with another student outside of GSoC to put together a testsuite and testing program which will help us assert that ~gccrs~ produces code with correct semantics (as a reminder, correct means "with ~rustc~'s semantics"). It is important for ~gccrs~ to only accept the correct subset of code, but it is also necessary that the assembly we produce has the same meaning and the same runtime characteristics as any other Rust program. This ties into our pursuit of producing a "correct" compiler, which we'll talk about more in a future blogpost in cooperation with the Rust project.
 
-In terms of technical contributions, we have closed the ~Unhandled attributes~ milestone, which covered the handling of all attributes required for compiling ~core 1.49~. We have made good progress on the ~Lang items~ milestone, with the only remaining step being to switch our existing code generation of lang item paths to these new paths we introduced. This will help all of our early code generation pipeline, namely surrounding built-in macros and the desugaring of certain constructs like ~for~ loops. Once this is done, we will fix the issues surrounding iterators and indexing, which currently prevent ~for~ loops from being completely implemented. We have gained a few new contributors this summer, and we hope that this trend continues. We hope they continue to contribute to the project, and will spend some time this week to try and help with the codebase when necessary.
+In terms of technical contributions, we have closed the ~Unhandled attributes~ milestone, which covered the handling of all attributes required for compiling ~core 1.49~. We have made good progress on the ~Lang items~ milestone, with the only remaining step being to switch our existing code generation of lang item paths to these new paths we introduced. This will help all of our early code generation pipeline, namely surrounding built-in macros and the desugaring of certain constructs like ~for~ loops. Once this is done, we will fix the issues surrounding iterators and indexing, which currently prevent ~for~ loops from being completely implemented. We have gained a few new contributors this summer, and we hope that this trend continues. We hope they continue to contribute to the project, and will spend some time this week to try and help with the codebase when necessary. For a look at the work we plan on doing this year, check out [[https://rust-gcc.github.io/2024/09/03/towards-gcc15.1.html][the engineering document we established a few months ago]]
 
 Finally, we would like to be more public about ~gccrs~'s progress. In some recent comments surrounding the Rust-for-Linux project, we have noted that some internauts believe that the work on the compiler has slowed down, despite our regular upstreaming and progress reports. We think this might be due to a lack of activity on social media and forums such as Reddit or HackerNews, and will start posting our monthly updates there again. We will also be coming out with a few blogposts in the coming weeks, namely around the progress achieved by our GSoC students and how it will impact users.