Rough agenda wg-macros history Project goals wg-macros history Vincenzo: About 1 year old, created in https://github.com/rust-lang/compiler-team/issues/637. RfL was considering using macros but there wasn't an obvious expert. Was debating whether to use syn, and if so how. Got involved with the edition, pair-programmed expr_2021 together.

2024-08-29 fmease's metavar test. // crate a //@ edition: 2018 #![macro_metavar_expr] macro_rules! make_matcher { ($name:ident, $fragment_type:ident) => { macro_rules! $name {

Playground: https://www.rustexplorer.com/ Date: Oct. 9th 2023 Last Weekly meeting agenda: https://hackmd.io/OKHKZwy_QsGE25QwoLgpgw Topics What expect from the triage meetinghttps://rust-lang.zulipchat.com/#narrow/stream/410876-wg-macros.2Ftriage/topic/triage.20meeting.202023-10-20 What do we mean by assignee?Assignee field on GitHub is kind of like a mutex, not everyone will know if wg-macros uses it differently so we might discourage new contributors if they see an assignee. Having someone listed as an expert or mentor would be good. Adding that as a comment on the issue is probably a good way to do that, at least for now. We want to make a PR for the Forge that defines E-mentor label.

ICE When Attempting to Format an AST /poll Action on ICE When Attempting to Format an AST #114874? Request and wait for a Minimal Reproducible Example (MRE) without syn Attempt to debug the various causes from the stack trace Ignore because the issue isn't deterministically reproducible Error Output Improvement: Semicolon Usage Leads to Multiple Potential Developer Errors Issue link: Rust Issue #111316 Playground: Rust Playground Link

Playground: https://www.rustexplorer.com/ Date: Oct. 9th 2023 Last Weekly meeting agenda: https://hackmd.io/2of1Uu2oRbGgVIHVlgCy3w?view Topics Our meeting time Opinion on the agenda topics Pinged the t-compiler for an official calendar, and hackmd note team Notes

Date: Oct. 6th 2023 Meeting: https://jitsi.member.fsf.org/wg-macros Participants:@vincenzopalazzo @danielhenrymantilla Lukas Arthur Topics vincenzopalazzo Q: What is the wg idea on how to organize the jobA: Moved the questionin another time after we run some experiments

https://github.com/rust-lang/rust/issues/112850Patch: None Possible solution https://github.com/rust-lang/rust/issues/112850#issuecomment-1732280859 https://github.com/rust-lang/rust/issues/74497 Patch: None Possible Solution https://github.com/rust-lang/rust/issues/74497#issuecomment-1534485733 https://github.com/rust-lang/rust/issues/93674

Rust Foundation Fellowship Application Form Please tell the name by which you choose to be known. * What are your pronouns? What is your email address? Please provide a link to your GitHub account. Please provide links to personal website/public social media handles/LinkedIn (as appropriate) * Where are you based? What is your primary language of communication?

Report for the crater run in https://github.com/rust-lang/rust/pull/103029#issuecomment-1578135208 The test regression caused by the expansion_growth_limit are the following one https://crater-reports.s3.amazonaws.com/pr-103029-1/try%233260e8859c0ff2d67d3a723d758f74881c2fe40a/gh/123dou.learnRust/log.txt [INFO] [stdout] error: expansion grow limit reached while expanding `vec!` [INFO] [stdout] --> finished/src/word_search_2.rs:123:13 [INFO] [stdout] | [INFO] [stdout] 123 | / vec![

This is an issue template for the preparation of the compiler-team issue. Responsibles of this issue: @vincenzopalazzo Zulip Stream: t-compiler/macro-wg initiative propose Current main point of discussion Proposal This proposal aims to establish a "macros-wg" with both basic and advanced goals. The advanced goals will be pursued in the future only if, after one year, this work is confirmed to be effective through another MCP. Currently, the macros system in the compiler is more like a "dead zone" where it is difficult to make any progress with nightly features that have been in nightly forever or propose new changes or bug fixes.

Overview Problem Idea Conclusion Problem One of the problems with the Rust compiler is that macros are a neglected area of the compiler. While many people use them, there are fewer and fewer individuals who have a deep understanding of how they work. A couple of common bugs, such as the issue #[105830], serve as examples of this issue. I had a difficult time getting my PR at https://github.com/rust-lang/rust/pull/103029 reviewed, and even then, it was challenging to receive feedback from people who are familiar with the code base.

Overview Introduction Pieces of Tokio Introduction From out previous chat in zulip we talk about the content in the notes Some of the open question is how Tokio expand the macros on top of the main function, and tests, so I make some research and this is the result

Table of Content Reference Mentor available Mentor Contacted Reference Most of the mentors that I found are listed in the following web page https://rustbeginners.github.io/awesome-rust-mentors/ Mentor available The first mentor that I find on the following web page https://rustbeginners.github.io/awesome-rust-mentors/ are

[ ] Move the error message:from:4 | async_fn() | ^^^^^^^^^^ expected u8, found opaque type to:4 | async_fn() | ^^^^^^^^^^ expected `u8`, found future [x] move the note message: from:note: while checking the return type of the `async fn` --> test.rs:2:28

PR: https://github.com/rust-lang/rust/pull/103902 original reason: implied bounds for hir typeck fn foo<'a>() { let x = |x: &'_ &'a ()| { // ^^^^^^^^^^ inside of the closure, we know `'a: '_`. body }; }

Reference issue https://github.com/vincenzopalazzo/async-main-and-tests-initiative/issues/1 This document is part of the async main initiative and the goal is to make a small summary of the historical issue and solution proposed to be able to support async main and test functions, with hope that we could make a good starting point for the initiative for the 2023. Table of Content What is the goal of the initiative? Where we are? How my vision for support this feature looks like Conclusion

Sel configure the compiler Help of https://rustc-dev-guide.rust-lang.org/getting-started.html Felix's suggestion: Based on https://www.youtube.com/watch?v=oG-JshUmkuA Keep the stage 1 when you recompile (not alwals possible, see office hours) Fixing issue https://github.com/rust-lang/rust/issues/92898

Owner: async-wg Date: 1668508708/11/2022 New Issues async block with futures::stream::Buffered is not Send in date 2022-11-13T22:34:24Z Do we need Send bounds to stabilize async_fn_in_trait? in date 2022-11-01T23:06:07Z Stabilize ::{core,std}::pin::pin! in date 2022-10-31T12:21:20Z New example of higher-ranked lifetime error in date 2022-10-25T09:33:38Z

title: "Write an Async Runtime: Basic Concept" image: "/async-rust/async-rust.svg" tags: "Rust Lang" "Async Rust" In this blog post we will talk about the basic concept that are around an async runtime in rust, and also the basic concept of the async paradigm.

Road Map Async main and tests Zulip Thread State of the art