Engineering.wustl.edu

E81 CSE 5402 (section 1): Concurrency and Memory Safe System Software Development

Professor: Chris Gill
Co-Instructor: Zhuoran (Jordan) Sun
Teaching Assistant: Daniel Palmer
e-mail: cdgill@wustl.edu
e-mail: zhuoran.sun@wustl.edu
e-mail: d.m.palmer@wustl.edu
Office hours: by appointment in McKelvey 1039
Office hours: Mondays 10-11am and Fridays 2-3pm in McKelvey 3037
Office hours: Tuesdays and Thursdays 11:30am-12:30pm in McKelvey 3037

Fall 2026

Course web page: http://www.cse.wustl.edu/~cdgill/courses/cse5402/

Course Piazza page: https://piazza.com/wustl/fall2026/fall2026cse540201/home

Exam 1: 10-11:20am Thu Oct 8 in Green L0120 (Rodin Auditorium)

Exam 2: 10-11:20am Thu Nov 19 in Green L0120 (Rodin Auditorium)


Contents

  1. Times and Locations
  2. Course Description and Learning Objectives
  3. Prerequisites
  4. Discussions/Studios
  5. Labs
  6. Textbooks and Other Resources
  7. Grading
  8. Academic Support, Health and Wellness, and Disabilities
  9. Title IX, Diversity, and Inclusion
  10. Academic Integrity and AI Use Policy


Times and Locations

Lectures/Discussions/Studios: In-Person in Urbauer 218, 10-11:20am Tuesdays and Thursdays


Course Description and Learning Objectives

As multi-core processors and multi-threaded programming are ever more prevalent in modern computing systems, ensuring correctness of programs depends strongly on avoiding hazards that may arise from concurrency and memory management semantics in those contexts. This course focuses on the memory safety and concurrency safety models in Rust, with an emphasis on the language's syntax and semantics related to those models, both separately and in combination, as well as a general coverage of the language as a whole. Lectures and assigned readings will be augmented with studio exercises and laboratory assignments in which key language features will be explored and applied hands-on.

Learning objectives in this course include:

  1. conceptual and practical experience with safe memory management including ownership, ownership transfer, mutable and immutable borrowing, in Rust;
  2. conceptual and practical experience with safe concurrency and synchronization including fork-join semantics, channels, and lower-level primitives, in Rust;
  3. conceptual and practical experience with concurrency and event handling patterns and idioms in Rust;
  4. introductory experience collaborating with Generative AI in concurrency and synchronization design; and
  5. overall experience with and mastery of the Rust programming language and its libraries

Prerequisites

Operating Systems Organization (CSE 422S under the old numbering system, CSE 4202 under the new one), or graduate standing and prior experience with concurrency, synchronization, and memory management.

Discussions/Studios

This course is offered in a studio/lab format, to emphasize active learning through hands-on participation. Except for a few open lab sessions, and the days when exams reviews and the exams themselves are held, you will work in small groups on studio exercises that will emphasize three main topics: (1) memory safety, (2) concurrency safety, and (3) Rust language syntax and semantics.

Reading materials will be assigned for many of the topics. It is to your advantage to go over the readings prior to class time, and to ask questions about anything that may be unclear. Supplemental resources including web materials and additional books that may be helpful also may be suggested.

Dates
Topics
Readings/Resources
Assignments
Tue Aug 25 Course Introduction
Academic Integrity
CSE 5402 AI Use Policy
About Rust
BOT Chapter 1
(optionally KN Chapter 1 and G pp. xxi-xxiii)
 
Thu Aug 27 A Tour of Rust
Error Handling
Crates and Modules
BOT Chapters 2, 7 and 8 and pp. 535-540
(optionally KN Chapters 2, 7 and 9 and G Chapters 1, 4 and 5 and pp. 74 and pp. 207-243)
Studio 1
Tue Sep 1 Types in Rust
Structs
Lab 1 overview
BOT Chapter 3 and 9
(optionally KN Chapters 3 and 5 and G pp.48-50)
Studio 2
Lab 1 assigned
Thu Sep 3 Ownership and Moves BOT Chapter 4
(optionally KN pp. 59-70 and G pp. 7-8 and pp. 45-46)
Studio 3
Tue Sep 8 References BOT Chapter 5
(optionally KN pp. 71-83 and G pp. 9-12 and pp. 155-156)
Studio 4
Thu Sep 10 Expressions BOT Chapter 6 Studio 5
Tue Sep 15 Enums and Patterns BOT Chapter 10
(optionally KN Chapter 6)
Studio 6
Thu Sep 17 Traits and Generics
Utility Traits
BOT Chapters 11 and 13
(optionally KN Chapter 10 and G Chapter 3)
Studio 7
Tue Sep 22 Closures
Operator Overloading
BOT Chapters 12 and 14 Studio 8
Thu Sep 24 Iterators
Lab 2 overview
BOT Chapter 15
(optionally KN pp. 284-294)
Studio 9
Lab 2 assigned
Lab 1 due 11:59pm Fri Sep 25
Tue Sep 29 Collections
Strings and Text
BOT Chapters 16 and 17
(optionally KN pp. 141-147 and pp. 154-159)
Studio 10
Thu Oct 1 Exam 1 Review Studios 1-10 due by 11:59pm Wed Oct 7
Tue Oct 6 Fall Break (no course meeting)
Thu Oct 8 Exam 1 10-11:20am in Green L0120 (Rodin Auditorium)
Tue Oct 13 Concurrency I: Fork-Join Parallelism
Concurrency II: Channels
Concurrency III: Shared Mutable State
BOT Chapter 19 pp. 499-511, pp. 512-525, pp. 525-540
(optionally KN pp. 353-361, pp. 361-367, and G Chapter 10)
Studio 11
Thu Oct 15 Concurency Patterns: Active Object, Half-Sync/Half-Async, and Leader-Followers
Lecturer: Jordan Sun
  Studio 12
Tue Oct 20 Agentic Programming with Concurrency and Synchronization
Lecturer: Jordan Sun
  Studio 13
Thu Oct 22 Input and Output
Lab 3 overview
Lecturer: Jordan Sun
BOT Chapter 18 Studio 14
Lab 3 assigned
Lab 2 due 11:59pm Fri Oct 23
Tue Oct 27 Macros BOT Chapter 21
(optionally KN pp. 449-458 and G Chapter 7)
Studio 15
Thu Oct 29 Unsafe Code BOT Chapter 22
(optionally KN pp. 420-429 and G Chapter 9)
Studio 16
Tue Nov 3 Foreign Functions BOT Chapter 23
(optionally KN pp. 426-427 and G Chapter 11)
Studio 17
Thu Nov 5 Asynchronous Programming I: Synch to Asynch BOT Chapter 20 pp. 541-566
(optionally G Chapter 8)
Studio 18
Tue Nov 10 Asynchronous Programming II: Using Asynch Mechanisms BOT Chapter 20 pp. 566-599 Studio 19
Thu Nov 12 Event Handling Patterns: Reactor and Proactor   Studio 20
Tue Nov 17 Exam 2 Review Studios 11-20 due by 11:59pm Wed Nov 18
Thu Nov 19 Exam 2 10-11:20am in Green L0120 (Rodin Auditorium)
Tue Nov 24 open office hours to work on lab 3
Thu Nov 26 Thanksgiving Break (no course meeting)
Tue Dec 1 open office hours to work on lab 3
Thu Dec 3 open office hours to work on lab 3
Lab 3 due 11:59pm Fri Dec 4th


Labs

There will be 3 lab projects this semester, which will be turned in via Canvas, and will be graded and returned to you electronically as well. Each lab assigment will give details of the procedure for turning in the lab. Labs will increase in length, value, and difficulty throughout the semester. The exact due date will be specified in each lab description.

Each lab will require a lab report. Report format and length and content requirements will be described in each lab assignment. The actual report will be submitted via e-mail, as well, so it must go into a file.

Labs will be performed in teams of 1, 2 or 3 people (but not more than 3): teams may be different for each lab assignment or may remain the same for all labs. Each team should submit its solution and lab report for each project.

Labs submitted within 24 hours after the posted deadline will be accepted with a 10% penalty up front, and labs submitted between 24 and 48 hours after the posted deadline will be accepted with a 20% penalty up front. Labs submitted after that will not be graded except in the case of extenuating circumstances approved by the professor.

You may discuss your lab projects with other students outside your team only during course meeting times. Discussion of lab projects within a team, is encouraged at any time. Each team must design and implement its own solution, and prepare its own report.

The following lab assignments have been posted so far in the course:


Textbooks and Other Resources

Required text:

We'll use the required textbook both for class material and as a reference. Revelant portions of the required text will be assigned throughout the semester: please read each assigned section before the course meeting where it will be discussed.

Optional texts:

Readings in the optional textbooks also will be suggested, for enrichment and to complement the assigned readings in the required text.

Please read through the CSE 5402 Programming Guidelines and follow them as you develop your studio and lab solutions this semester.

The Learn Rust page has links to documentation about the Rust language, libraries, and tools.


Grading

Labs and studios will constitute a major portion of the grade in this 3-credit course. This reflects the course's emphasis on hands-on exploration of the material. Labs will be graded for quality of design, implementation, and documentation. Studios will be graded for completion of all the required exercises, though grading comments may be provided as feedback even if a studio is marked complete.

The in-semester exams will be roughly proportioned to cover the material in all other aspects of the course: readings, lectures, studios, and labs. The best way to study for the exams is to keep up with the readings, lectures, studio exercises, and labs during the semester. The first exam will cover the material up to that point in the course, and the second exam will cover the material after the first exam.

Your semester grade will be determined as follows, with an overall weighted average of 90% corresponding to at least an A-, of 80% corresponding to at least a B-, and of 70% to at least a C- (and to a passing grade if the course is being taken P/F rather than for a letter grade):

Labs 50 percent
   Lab 1:  10 percent
   Lab 2:  15 percent
   Lab 3:  25 percent
Exam 1 15 percent
Exam 2 15 percent
Studios 20 percent


Academic Support, Health and Wellness, and Disabilities

We encourage everyone to take a look at, and potentially make use of, the many academic support resources available at Washington University in St. Louis, including: The Learning Center, and The Writing Center, and Student Technology Services.

Washington University recognizes that students serving in the U.S. Armed Forces and their family members may encounter situations where military service forces them to withdraw from a course of study, sometimes with little notice. Students may contact the Office of Military and Veteran Services at (314) 935-2609 or veterans@wustl.edu and their academic dean for guidance and assistance.

The Habif Health and Wellness Center, WashU Cares, Center for Counseling and Psychological Services, and RSVP are important university resources for issues pertaining to physical and mental health.

Students with disabilities or suspected disabilities are strongly encouraged both to bring any additional considerations to the attention of the instructor and to make full use of Washington University's Disability Resources, potentially including accommodations for studios, labs, and/or exams.


Title IX, Diversity, and Inclusion

Washington University is firmly committed to addressing and preventing sexual misconduct on our campuses: please see the Washington University statement on new Title IX rules. If a student discusses or discloses an instance of sexual assault, sex discrimination, sexual harassment, dating violence, domestic violence or stalking, or if a faculty member otherwise observes or becomes aware of such an allegation, the faculty member will keep the information as private as possible, but as a faculty member of Washington University, they are required to report it immediately. Additionally, incidents or complaints can be reported to the Office of Student Conduct and Community Standards or by contacting WUPD at (314) 935-5555 or contacting your local law enforcement agency. To explore options for medical care, protections, or reporting, free and confidential support resources and professional counseling services are available through the Relationship and Sexual Violence Prevention (RSVP) Center in Seigle Hall, Suite 435, which can be reached at rsvpcenter@wustl.edu or at (314) 935-3445. For after-hours emergency response services, call 314-935-6666 or 314-935-5555 and ask to speak with an RSVP Counselor on call. Washington University's Center for Diversity and Inclusion supports and advocates for undergraduate, graduate, and professional school students from underrepresented and/or marginalized populations, collaborates with campus and community partners, and promotes dialogue and social change to cultivate and foster a supportive campus climate for students of all backgrounds, cultures, and identities. The University has a process through which students, faculty, staff, and community members who have experienced or witnessed incidents of bias, prejudice, or discrimination against a student can report their experiences to the University’s Bias Report and Support System team. For procedures and information on reporting an instance of bias, please visit the Bias Report and Support System page on the Center for Diversity and Inclusion web site. Please see the Office of the Registrar's Biographical/Demographic Student Information Changes page for additional information and resources.


Academic Integrity and AI Use Policy

Each studio and lab assigned in this course is expected to be completed collaboratively by up to three people (and not more than that). Student teams may change from assignment to assignment, but the sharing of code between teams without prior permission of the instructor is strictly prohibited, and you must acknowledge and document in detail all contributions that anyone has made to the work.

Please also read and familiarize yourself with the CSE 5402 AI Use Policy. While you are encouraged to leverage the capabilities of Generative AI (GenAI) in this course, you must also maintain and develop your own critical thinking, directive agency, and overall authority in your collaborations with GenAI agents and services. You must also design your interactions with GenAI so as to support the standards of transparency and documentation and citation that are spelled out in that policy.

Exams must be completed individually without assistance from any other person and without reference to materials or devices, except as specifically allowed by the instructor (documentation of what is allowed will be described in class, provided in the corresponding exam review slides, and written on the font page of the exam).

Cheating costs everyone something. Someone who cheats misses out on the intended opportunity to improve through the assigned work, and like anyone helping them cheat is at risk of diminished reputation as well as specific sanctions. Cheating also degrades the value of the degree earned by those who complete their work with integrity. If you have any doubt about whether something is allowed under the academic integrity policy for this course, please ask your instructor first.

Academic integrity is itself worth studying and thinking about as a key component of your education. Please read, familiarize yourself with, and reflect on the McKelvey School of Engineering's and Washington University's undergraduate and graduate policies on academic integrity.