Posts tagged "maintainer-spotlight" | Rust Blog

Maintainer spotlight: Alejandra González (@blyxyas)

2026-09-21T00:00:00+00:00

There are hundreds of people who maintain the Rust toolchain, often on a volunteer basis on top of another job. The Rust Content team is working on a series of blog posts highlighting some of these prolific contributors to recognize the awesome work that they are doing in order to make Rust better for everyone. You can find the previous post here. Consider donating to the Rust Foundation Maintainers Fund if you'd like to support Rust Project maintainers.

In this post, we would like to introduce Alejandra González (@blyxyas). Alejandra started contributing to Rust around four years ago. She primarily works on the Clippy linter as a part of the Clippy team, which she joined in 2023. She is helping other people starting their Rust and Clippy contribution journeys, and recently, she became one of our first Maintainers in Residence!

We interviewed Alejandra to find out how she started contributing to Rust, and why she considers performance to be so crucial. Read more below!

Can you briefly introduce yourself and your background?

Hi, I am Alejandra González, also known as @blyxyas. I was born breathing the mediterranean sea brew, or, in other words, I am from Spain. When I was around thirteen, I thought that I should learn something that will pay off in the long run, and what better than programming?

I started with JavaScript and web development, but it didn't feel like my thing, because I like to make fast things, and this technology didn't allow me to do that. I also tried C++ for a while, but didn't like it very much. Then I discovered Rust through a YouTube channel, on the archaic version 1.45, and I was immediately hooked. The borrow checker, traits, macros, it was mind-bending at first, and it felt great.

How did you learn Rust?

Primarily through Rustlings, which I really like. I think that many programming language learning materials are not that great. They are either extremely beginner, or extremely advanced.

Everyone knows what's a loop, they look pretty much identical in every single language, on the other hand, I had no idea what an enum is, and I had to find out! Rustlings really hits that sweet spot, where things are a bit challenging, but you can still solve them within half an hour.

The Rust book is of course also an incredible learning material. It is probably the only book that I would actually recommend for learning tech-related things. It is unparalleled.

How did you start contributing to Rust?

While using Rust, I was constantly thinking that it is neat, but there are little things missing, which could make it so much better. I had this itch to improve it, as it didn't completely live up to my expectations, it was a 9 out of 10.

So I opened the Rust contribution guide, and started learning Git so that I could open my first pull request (PR). The guide suggested contributing to Clippy as a good onboarding project, so my first contribution was adding a new lint to Clippy. The lint warns users if they misuse the caret (^) operator, because unlike in some other programming languages, it represents the Exclusive OR (XOR) operation and not exponentiation.

While working on my first pull request, I created a lot of weird and broken Git commits and pushes. It was extremely embarrassing, and I felt that I was wasting everyone's time. I was thrilled once the lint was in a ready state to be merged, until my reviewer uttered the words "squash those commits"... I didn't know much about Git back then, as I was learning it on the spot. So I tried to watch a tutorial on squashing commits; it wasn't enough. My attempts didn't end well, and I managed to pull unrelated changes from another branch and made a mess. I suppose that this has happened to everyone at least once :)

It is a bit weird to look back at it today, now that I am helping other contributors make their own Clippy PRs.

Overall, I think that contributing to Clippy is much easier than to add a new feature to the Rust compiler, for example. It is thanks to Clippy's architecture that even though we have over 800 lints, each one of them is standalone, and you can understand most of them just by reading a single Rust file. When you think of a new lint, it's almost guaranteed that someone in the codebase has already had a similar idea to yours, so you can mix and match parts of other lints to make a new creation.

How did you join the Clippy team? Did you have a mentor?

A lot of people were mentoring me, but one Clippy maintainer, xFrednet, stood out. He had a wonderful vibe, not only because of his technical knowledge, but also due to the way he interacted with other contributors. Thanks to him, I felt completely welcome in the Rust Project, and it molded the way that I talk to new contributors. It's much more productive to have a travel guide as a maintainer, ready to take you by their side; than to have only a code guardian, only focused on the code quality.

After I had mastered the arts of the Clip, xFrednet invited me to the team, and here we are now.

The thing that keeps me going since then are the people in the Rust Project. It is astonishing how many wonderful people consistently work on the same project. I think that many people go to Rust for the promise of good technology, and actually stay for the people. This was also my case.

You are now also mentoring other contributors. What does it mean to you to be a mentor?

There are people reaching out to me, wanting to get started contributing to Clippy. They bring expertise from different sectors, with different personalities, and all are coming together to make a code linter a bit better. I think that it is really great when beginners call out to you to help them solve their problem.

Even without going into mentoring, meeting so many cool people feels great. In the past two years, I've been in contact with the Rust for Linux team. And I really like that there is a mutual relationship with the Rust for Linux project, having a portion of Linux developers reach to teams at Rust is amazing. I love Linux, I use it every day, and I think it is one of the most important pieces of technology ever created. So seeing that they are adopting Rust fills me with pride. It kind of validates that what we're doing is having a real, positive impact in the world.

What are you working on in Rust at the moment?

My primary goal is to improve the performance of the Rust compiler and Clippy. We've talked a lot about Clippy, so apart from it I'm currently working on a Project Goal which is focused on improving the incremental machinery inside in the compiler, as to reduce useless recompilations, and make it overall faster. It's a big task and an exciting plan, but it takes a lot of work and cross-team discussions to make progress in this area.

It's both much easier and much harder than you think.

Why are you interested in improving performance?

When I started programming, I had a really slow computer, with the (in)famous Pentium 4 CPU, so my hardware was extremely underpowered for the things I wanted to do. Simply because of the money I had available, I was limited to the things I could achieve.

Today, I find that horrible, because we are essentially gate-keeping a language that has turned into a very important technology in recent years, to people who can afford powerful hardware. I want people to not have to spend their whole fortune to get a computer powerful enough for programming in Rust. The day that a Raspberry Pi could compile a whole Rust workspace in less than a minute, that day I can retire with a clean conscience (and go improve performance at Zig). But that is certainly not currently possible.

And also there is the whole aspect of not killing our planet as fast by producing more performant software. I fundamentally think that we are not entitled to kill the planet just to further our technology, without thinking about the impact.

You recently became one of the first Maintainers in Residence. How does that feel?

It is amazing! When I first started on Clippy, I was really excited, I reviewed a lot of pull requests, and did a lot of the (sometimes a bit boring) maintenance work in my spare time. As with pretty much everyone, at one point the burn out creeps in. Open source is an infinite amount of work; there is always another pull request to review, another issue to solve, another feature to add, because anyone can open a PR or an issue or request a feature. It is very tiring over a long time period.

Being a Maintainer in Residence means having financial support to do what needs to be done. I am now reviewing several pull requests per day, and taking the necessary time for each one. Without taking shortcuts, without doing less quality work. That is something I would have never dreamt of, and it really takes a huge burden off my back.

Before, whenever I was doing maintenance, I always had this doubt: should I do something else with my life? Should I get a boring office job and work in a corporate environment, or maybe go back to studying? Now I don't have to worry about that, which really helped reshape my life. I live in a medium-sized town in Spain, so the help that the MiR program provides is huge in comparison to my expenses. It completely takes off that anxiety and those doubts. For now, I'm able to do what I love, and I have no words to describe how great that feels.

That being said, I also have to remind me that it is okay not to work all the time. Sometimes, I'm insecure about the value I bring to Rust and the people and companies funding me. To combat that, I really like this quote: "You are able to take a break, and Rust will not break without you."

Would you like to share anything else with the Rust community?

Now more than ever, we've been getting bad news in the technology sector. Job offerings have been fewer and layoffs are taking over many people's careers. It seems that every couple of weeks we find ourselves in a new all-time crisis. I want to reassure people that technology exists as proof of humankind's resilience. In the age where it seems like the machine is engineered to work against us, the Rust team is dedicated to have a more humane language. Please stick around to see it bloom.

Also, incremental compile-times are going to SHATTER in the next very few years. That's it, that's the announcement. Please stick around for it.

We thank Alejandra for sharing her thoughts with us, and for all her work on improving Clippy and Rust!

Maintainer spotlight: Gen Li (@rami3l)

2026-07-07T00:00:00+00:00

In this post, we would like to introduce Gen Li (@rami3l). Gen started contributing to Rust around four years ago. In 2023, he joined the Rustup team, and in 2025 he became the lead of this team. Apart from working on Rustup, Gen Li also mentored several Rust contributors as a part of Google Summer of Code (GSoC).

We interviewed Gen to find out how he joined the Rustup team and what are his thoughts on coding as a social activity. Read more below!

Can you briefly introduce yourself?

Hi, my name is Gen Li. I come from Chongqing, an industrial city in southwestern China. I studied engineering and computer science at École Centrale de Pékin in Beijing, and I also went through a study exchange program in France, where I studied at the Centrale Nantes engineering school. After I graduated, I worked in China for a while, and last year I moved to Paris, so now I am based in France.

How did you start with Rust?

During my university studies, I was working with Python a lot, mostly to automate various processes, such as analyzing lab data. I got annoyed by Python a little bit, because it was hard to write correct code, and the package management story at that time was quite confusing^[1]. When I wanted to dive deeper and figure out how things in Python are actually implemented, I realized that it is often done in other languages, such as C, Cython or Fortran, which seemed quite complex.

In 2019, my friend @lynzrand introduced me to this cool new language that he has been playing with. I decided to try it, and then took it as a personal challenge to try to learn all the new concepts that I found in Rust. My first experience of building something serious in it was helping that friend build a component for an online service used for teaching classes.

What impressed me a lot about Rust was the whole developer experience and its tooling, such as the compiler or Cargo. Especially the whole unified process of creating, packaging and shipping a Rust project and the great documentation and error messages that guide you along the way.

I also examined other technologies and spent a lot of time learning (and fighting!) their tooling, and found that Rust really hit the sweet spot, so I decided to stick with it.

How did you get involved with the Rust Project?

I wanted to explore what it takes to create good tooling, and what makes Rust such an extraordinary experience. What I found great is that software in the Rust Project is written in Rust wherever possible, which means that it is not necessary to master multiple languages to make adjustments to the toolchain, and every improvement that we make to Rust then directly helps its contributors, which is something that I am really fond of.

My first contribution was to the wider Rust ecosystem. When writing a small Rust automation tool that used clap for argument parsing, I found out that clap had a bug. I was able to investigate it and fix it, so I was able to make a meaningful contribution to clap. Contributing to this project also led to my first interaction with Ed Page, a member of the Cargo team, who maintained clap.

That was a really nice experience, so I wanted to contribute more to "famous" Rust projects. I continued with scratching my own itches, so after I found a bug with derive expansion in Rust Analyzer, which I was using daily, I sent my first pull request to the upstream Rust toolchain. At that time, I was still a "drive-by" contributor, mostly fixing the bugs that bothered me, but I eventually wanted to participate more.

How did you join the Rustup team?

Weihang Lo, a Cargo contributor who organized a large Telegram Rust community that I was a part of, told me that the Rustup team was in danger. That was surprising to me, because at that time I thought that Rustup was very stable and that it doesn't need any new development, and could stay as-is "forever". Of course, now I know that is not the case.

Robert Collins, the only Rustup team member at that time, was calling for help. Given that I already had an intermediate knowledge of Rust, I thought that I could probably help maintaining it to get it out of the hardship that it was experiencing at the moment. So I contacted Robert and tried to do some basic maintenance tasks, starting from trivial fixes, and later also implementing larger features.

A few months later, I was invited to the Rustup team, together with Dirkjan Ochtman, a very experienced Rust maintainer. Together, we kind of restarted the maintenance of Rustup, and we have been maintaining it ever since. In 2024, Chris Denton joined the team, bringing invaluable Windows expertise.

How did joining the Rustup team affect your perspective on it?

Rustup is a crucial component of the overall Rust developer experience, which excels thanks to different tools (compiler, Cargo, Rustup, etc.) being tightly integrated and working well together. Contrary to what I used to think, it actually requires quite a lot of maintenance! We have to keep up both with changes to the Rust toolchain and its components, but also changes to operating systems. We also try to optimize its performance, due to the list of components and Rust targets growing over time, both in size and count. It is not possible to simply stick to what was done in the past ten years; we constantly have to adapt. This was a big mental shift for me.

Another thing that surprised me was the social aspect of contributing to open source. I used to think that the Rust Project had to be managed by some mysterious mechanism that I didn't understand, which would organize and structure work and provide resources to contributors. I learned that this is currently far from reality, and that almost everything is self-directed. For anything to happen, someone has to actively produce an effort to do it. Everyone is focusing on the one aspect that matters to them, and there is essentially no top-down management.

In general, I am happy that I am a member of the Rust Project, because I love helping other people out and volunteering, but it is also an incredible learning experience for me. I am constantly learning new things, even about Rustup and its various subsystems, which were developed over time by many people before me.

What have you been up to in the Rustup team since you joined it?

Between 2023 and 2025, it seemed that little has changed with Rustup, despite several new releases and minor bugfixes being released. However, in reality, we have done a lot of refactoring and modernization work, such as reworking the logging system and finalizing the migration to tokio, which was possible thanks to Robert's prior efforts. This work was quite important for the long-term health of Rustup's codebase, although most Rust users probably did not notice any changes during this period, because it all kind of happened behind the scenes.

In 2026, we have finally started shipping user-visible UX improvements, such as the new command-line interface style and toolchain installation acceleration, which has received a lot of praise from the community. It should be noted that these changes simply wouldn't be possible without the aforementioned maintenance groundwork. It is this long-term work that has brought us the nice results we see today, and I really wish to make that sustainable.

In the past two years, you were a mentor in the GSoC program. What was that like?

Even though the Rustup team is now in a better state than it was a few years ago, we still need to find new contributors to meet the ever-growing demand for new Rustup features and improvements, and to reduce our bus factor :) That is why I decided to participate in Google Summer of Code last year, as it is a great opportunity to onboard new contributors, and it makes me very happy that I can mentor them. While I could implement a new feature myself, it is much better to guide someone to work on it.

I'm very happy that last year we found Francisco Gouveia, whose GSoC project was focused on making Rustup concurrent and thus making toolchain installation faster. This project had great results, and helped optimize Rustup downloads across the globe. Francisco has been super helpful all along the project, and we saw a lot of potential in him, which is why we invited him to join the Rustup team after his GSoC project concluded. That is a real success story! Now I am looking forward to this year's GSoC project.

I am constantly learning new stuff while mentoring, which is great. I also learned that mentoring is all about communicating, and it helped me improve my responses in various situations, both professionally and personally.

You seem to have a lot of things on your plate. How do you find the time to contribute to Rust?

That's not an easy question to answer for me. On the one hand, Rust has always been my passion, and I am still very motivated to contribute, which is also why I constantly come back to help with various things, even at weekends or during the night. I also have many ideas on what to improve in Rustup if I had enough time for it, e.g. implementing toolchain deduplication or repairs.

But on the other hand, after my graduation, I have to prioritize my professional life, and also life outside code. I still have some spare time, but it is very hard to find long uninterrupted time slots that would allow me to focus on complex fixes or even major redesigns of Rustup to address some of its long-standing problems.

I know now that the risk of open source burnout is real. Sometimes things feel stressful and unpredictable, and it sometimes comes to me that holidays don't actually feel like holidays anymore, because I have to bounce between multiple things.

Currently, I am actively looking for opportunities to find funding for my work on Rustup, and potentially also other relevant projects that I could help out with, such as bootstrap (the Rust compiler build system) or the release process of the Rust toolchain.

What advice would you give to someone who would like to contribute to Rust?

For a start, it is good to start engaging with the Rust Project! Even if it is a small thing. I know many contributors who started their stories by fixing small issues that bothered them, such as making typo fixes or documentation enrichments, and later expanded to work on larger features. When your contribution resolves a real problem for your usage of Rust, it will give you more motivation to work on it. My contribution journey started by fixing tooling bugs that I encountered while using Rust, and through that I found a real purpose in contributing to Rust.

However, contributions do not have to be only technical. Open source is all about communicating and interacting with other people. You can make a difference simply by advertising what you are doing, for example by sharing your experiences with Rust in a certain domain. One of my contributions was that I have encouraged my schoolmate, @roife, to contribute to Rust, and now they are a regular contributor to Rust Analyzer and became a member of the Rust Project :)

Of course, you should remain constructive and not spam or harass people. Always interact with people responsibly!

Would you like to change something in the Rust Project?

If I had a magic wand, I'd use it to make maintenance and cleanup work get more attention and recognition. I think that we should also highlight the overall "health" of the Rust Project more often.

I believe that more people in the Rust Project should have the opportunity and means to continue doing what they are really good at. I believe in the power of individuals, and we should value that even more in our community. There are so many passionate and talented people working on Rust, and I would like them to see more recognition and more funding.

Would you like to share anything else with the Rust community?

Coding is a social activity, and a means of communication. If we can feel the love that others put into the code that they wrote, and bundle technical parts together with the human parts, then we will be able to achieve something greater in a more harmonious way.

We thank Gen for sharing his thoughts with us, and for all his work on improving Rustup!

That was before uv existed! ↩

Maintainer spotlight: Tiffany Pek Yuan (@tiif)

2026-06-03T00:00:00+00:00

In this post, we would like to introduce Tiffany Pek Yuan (@tiif). Tiffany started contributing to Rust only two years ago, as a Google Summer of Code (GSoC) contributor. Since then, she already became a member of the Compiler and Formality teams, and made substantial contributions to several projects, including the compiler, Miri and a-mir-formality. She also transitioned from being a mentee to a mentor, as she now mentors another contributor in the Outreachy program.

Currently, she is finishing her college degree while also working on the Rust compiler as a Rust maintainer intern in the RustNL Maintainers Team.

I got to know Tiffany as a GSoC student adding miri support for checking unsafe code in tokio. It was a joy to mentor her, and subsequently seeing her sticking around and learning about formality and rustc on her own.

Oli Scherer, Rust compiler team member and Tiffany's GSoC mentor

We interviewed Tiffany to find out about her experiences with joining the Rust Project and contributing to Rust. Read more below!

Can you briefly introduce yourself?

Hi, my name is Tiffany Pek. I'm currently studying a Bachelor's degree in computer science at the National University of Singapore. I should hopefully graduate in a few months! I contributed to various parts of Rust, right now I am focusing on a new trait solver bug fix that is related to implied bounds and modeling the borrow checker's semantics in the a-mir-formality project, which attempts to define a model of the type system.

How did you start with Rust? Did you learn it in one of your classes, or was it a hobby?

I did eventually attend a subject on Rust, but I already learnt it before that by myself. I heard about Rust around 2022, because I was searching for a systems programming language. I tried it for a research project and I really liked it. I tried a lot of programming languages before that, such as Java, Python or C++. They weren't bad, but Rust seemed much more enjoyable. What fascinated me about it were its really nice error messages.

How did you get involved with the Rust Project?

I remember telling my friend in college that it would be so cool to contribute to the Rust Project. Then, just a month later, I learned about Rust's involvement in Google Summer of Code (GSoC), and I immediately thought "I must join this program"! We all knew about GSoC at our university, but not many people tried to apply to it for some reason. I applied to GSoC and got accepted.

I think I would eventually contribute to Rust even without GSoC, but this internship gave me an opportunity to work on Rust almost full-time, without having to care about getting another job. That was very helpful.

How was your experience with GSoC?

I think it went really well! The experience was really enjoyable, because there were several other interns working on other projects at the same time. And all of us were kind of "newbies", so I wasn't the only person struggling with something. For example, when I messed up rebasing one of my pull requests, I saw that the same thing happened to another GSoC contributor, so I was like "oh yeah, we are the same!" and I didn't feel so bad about it. Also, Oli is a very nice mentor too, I had a lot of fun talking with them.

Jakub is also a really good organizer, which makes the program a huge success. I was really impressed by how we already discussed burnout even before the internship started.

Overall, it was a great onboarding experience, and it motivated me to stay as I really love the community.

What was your GSoC project about?

I worked on Miri, which is the undefined behavior detection tool for Rust. At that time, it wasn't really possible to run Miri on non-trivial asynchronous Rust programs that used the tokio crate. I added support for various non-blocking I/O syscalls (such as epoll) to it, in order to expand the set of programs that Miri can handle. We then worked with Tokio maintainers to run Miri on most Tokio tests in their CI, which was quite exciting.

What was your first contribution?

I added two tests to Miri. While doing so, I found out that the contribution documentation contained some unclear instructions, so I also improved it in the same PR.

Would you recommend that approach for new contributors?

Yes, I think that improving documentation is a good way to start contributing to Rust. It is also important to first locate areas that you are interested in, because the Rust Project is huge, there is Miri, the compiler, rustfmt, rustdoc, rust-analyzer, Cargo, and many other areas in need of contributions. Before making larger changes, it is always good to discuss them first with the corresponding maintainers before you open a PR.

If you are just starting with Rust, always read the error messages, because they are really nice. And if you find the error message difficult to understand, it might be a bug, so go open an issue!

What made you stay with Rust even after GSoC?

I stick around because of the community. During GSoC, I started talking to other Rust GSoC contributors. I ended up meeting two of them and other Rust Project members at a conference in Beijing. Subsequently, I made many amazing friends at the Rust All Hands, which makes Rust no longer a purely technical project, but also a hobby project me and a lot of my friends love and care about.

How did you join the Compiler team?

I started contributing to Rust in March 2024. I worked mostly on Miri during my GSoC project, but later I transitioned to working on the compiler. I was invited to join the Compiler team in November 2025. I didn't expect the invitation at all, so it surprised me.

At that point, I already interacted with the Rust community a lot, so it didn't feel like a large change to join the team, but getting officially recognized does feel really nice. I also think that being a Rust team member might help me with searching for a job.

Are you happy that you joined the Rust Project?

I am very happy about it! The people in the Project are really nice, and we frequently talk with one another, which is great.

I was able to attend the RustWeek conference and the Rust All Hands in 2025 and 2026, which was super nice. I'm grateful for the travel grant that I got from the Rust Project and Foundation, which allowed me to travel to these events. I made so many friends there, which is part of the reason why I am still staying with the Rust Project. All my Rust friends were there!

What excites you about working on the Rust compiler?

I find the compiler really exciting! It is like a mysterious black-box. If you do not know about how it works, it can seem scary, but once you start learning about it, it is actually quite neat to work with.

I find the new trait solver and Polonius work (the new borrow checking implementation) very exciting because they are the very core part of the language. Once the new trait solver is completed, we will be able to unblock a lot of features and fix many unsoundness bugs. And Polonius will allow the compiler to accept many correct programs that were previously rejected, which can make the language even more expressive.

What is it like to work in the compiler team, which is large and very visible?

The compiler team is so big^[1] simply because the codebase is very large, so everyone specializes in different parts of the compiler. I mostly only review parts of the compiler that I am familiar with. I never know what is going on in another part of the compiler, as there are just so many things happening every day.

Who is your biggest mentor in the Project?

It is multiple people, not just a single one. Initially it was definitely oli, because he was my GSoC mentor, and we talked (and still talk) quite a lot. Later I started working on type system stuff, where I help lcnr with the new trait solver. I also talk a lot with Boxy, who is now a co-lead of the compiler team.

Did you also try mentoring someone?

I try to leave easy improvements to other people, by opening issues for them that contain contribution instructions, and then try to answer questions from potential contributors on those issues. Recently I also started mentoring a contributor in the Outreachy program, which is exciting.

Would you like to change something in the Rust Project?

I know a lot of people who could produce awesome stuff if they had the opportunity to work on Rust full-time. But without funding, they have to work on and off, which is not very productive for them, and also bad for knowledge transfer. I wish more Rust contributors were funded.

Were you able to find funding for your own Rust contributions?

When I started contributing to Rust, I was funded by the GSoC program, which was nice. Later I joined an internship program at ETH Zurich, which also provided a source of funding. During those times, I was quite productive. But similar funding sources are usually only temporary. I am still a student, so I have to deal with my academic life, and I also need an extra job to support myself, which can be a bit difficult.

Finding a remote job can be tricky, because I live in Singapore, and the time zone difference is not that great. If I'm going to schedule a meeting with someone in the US, I usually have to do it at night. Luckily I don't go to sleep that early :-) But it can be an issue when interacting with people and companies from Europe or the US.

I hope to finish my studies soon, and after that I will have to get a full-time job. I think that I would still want to contribute to Rust even in that scenario, but I'm not sure yet how to do that. Maybe I would need to sacrifice my weekends a little bit, or something like that. It can be a bit difficult, but it is not impossible.

Right now, I have an internship in the RustNL Maintainers Team. It will be awesome if I can find a full-time job which allows me to work on Rust as I really love what I am doing now.

I think the upcoming funding efforts, such as the RustNL Maintainers Team and the Rust Foundation Maintainers Fund, will be able to financially support more Rust Project contributors. Though I am slightly worried about the incentives of companies funding maintenance work. Company interests are not always necessarily the same as the community's interests, which can create a bit of a conflict of interest. But I'm sure that there are ways to mitigate this.

We thank Tiffany for sharing her thoughts with us, and for all her work on improving Rust!

Currently, it has over 70 members. ↩