CSE 590 · Advanced Programming Languages · Winter 2026 · 4 credits
Overview
Programming languages and proof assistants are rich mathematical structures and powerful user interfaces. This course covers the design and use of advanced programming languages and proof assistants. We will build up systematically from mathematical first principles while considering human factors in language design, language prototyping, and techniques for reasoning about program behavior throughout the course.
The goal of the course is:
- To change the way you think about programming and programming language design in ways that will remain relevant across the many technology hype cycles that you will encounter over the course of your careers.
- To provide you with an introduction to contemporary tools and research results in the field of programming languages and theorem proving.
Prerequisites
This course assumes substantial prior programming experience and experience with rigorous mathematical definitions and proofs. No prior courses in programming languages or compilers are required, but the course proceeds quickly and students familiar with the topics at an undergraduate level are likely to be at an advantage.
Course Staff
- Instructor: Prof. Cyrus Omar (comar@umich.edu)
- GSI: Thomas Porter (thomasjp@umich.edu)
- Grader: Yuganshi Agrawal (yuganshi@umich.edu)
Lecture and Discussion
- Lecture: Mondays and Wednesdays · 1:30–3:00pm · FXB 1008
- Discussion: There will not be a formal discussion at the time scheduled by the registrar this semester.
Office Hours
Office hours will be held regularly by the instructors and GSIs, with times and locations announced on Canvas on the course webpage.
If an office hours session needs to be rescheduled, an announcement will be made on Piazza. Please check Piazza regularly to be sure that the office hours you plan to attend is being held as scheduled.
The office hours queue is linked on the course webpage. All office hours will use the queue.
Some office hours will be hybrid or fully virtual, in which case instructions will be provided for remote participants on the queue. You are encouraged, but are not required, to turn your videocamera on. For help with mathematical questions you are working on on-paper, you may be asked to take a photo of your work and send it to the person helping you, or hold it up to the camera. For help with coding questions, you may be asked to share your screen or a specific window. You can share your screen at any time without asking for permission.
Technology Requirements
Assignments require that you use a Mac, Windows, or Linux PC with a standard keyboard, an up-to-date copy of Firefox, Chrome, or a Chromium-based browser, and a PDF reader. We cannot guarantee that an iPad or other tablet will be sufficient. CAEN computer labs have suitable PCs available if you do not have one of your own, or if your own computer does not have sufficient power to comfortably run some of the software that we use in the course (which can be CPU-intensive at times). You will also need access to a cameraphone, digital camera, or scanner to be able to take clear photos of handwritten assignment solutions OR a tablet with a stylus. Assignments are submitted online, and we do not accept physical submissions.
Virtual office hours require that your device and internet connection are capable of sustaining clear audio and screensharing. A video camera is not necessary. You are welcome to turn video on during office hours calls if you would like, but it is not required.
Canvas
Assignments and major announcements will be made via the course Canvas site. Students enrolled in the course will be added to the Canvas site automatically. Grades will only be posted on Canvas at the end of the semester.
Webpage
The course webpage is linked from the course Canvas under Announcements.
Piazza
We will be using Piazza to host a course forum, which can be found linked from the webpage and Canvas. You are required to read Piazza regularly: we will post announcements and assignment clarifications there. In addition, it will be a significant source of help and hints on the assignments and projects.
We do not answer content questions via email. In order to save everyone time, we want all students to have the benefit of seeing each question and its answer, so please use Piazza. You can choose to hide your identity from other students (but not from instructors). Please search the forum before posting, to avoid questions that have already been asked and answered.
Do not post your own solutions, code, test cases, or output publicly to the forum. You may post questions that involve these things as a private question, which will be visible only to the staff. Otherwise, please favor public posts.
Please ask any questions you may have early. If you post them just before a deadline, we cannot guarantee that the course staff will be available to answer them in time, particularly outside normal working hours (9am–5pm M–F, excluding university holidays).
Recording Policy
Your participation in lectures, discussions and other recorded activities may be included in recordings. Recordings are intended for distribution only to students taking or auditing the course, and should not be distributed to others, whether or not they are within the university, without approval from the instructor.
Students are prohibited from recording/distributing any class activity themselves without written permission from the instructor or as necessary as part of approved accommodations for students with disabilities. Any approved recordings may only be used for the student's own private use.
Readings
For some of the lectures and discussions, we will post readings on the course webpage. Each reading is marked as either required or optional on the webpage.
There is no required textbook for the class. Instead, the assignment handouts include extensive expository material, and are required reading. However, the following textbooks may be useful for students who want an alternative presentation of the material, and optional readings from these books may be posted.
- TAPL: Benjamin Pierce. Types and Programming Languages. The MIT Press, 2002.
- PFPL: Robert Harper. Practical Foundations for Programming Languages (2nd ed.). Cambridge University Press, 2016.
- RWO: Yaron Minsky, Anil Madhavapeddy, and Jason Hickey. Real World OCaml (2nd ed., in progress). Available online here.
- PLFA: Philip Wadler, Wen Kokke, and Jeremy G. Siek. Programming Language Foundations in Agda. Available online here.
- PDTT: Carlo Angiuli and Daniel Gratzer. Principles of Dependent Type Theory. Available online here.
At least one copy of TAPL and PFPL are being held in course reserve at the Art, Architecture & Engineering Library for the duration of the semester. These can be checked out for no more than 3 hours at a time. The library also has online versions available to download.
Assignments
Over the course of the semester, we will assign homework assignments periodically. The exact schedule will be announced in lecture and on Piazza. A rough calendar of assignment due dates are available on the webpage, but these are subject to small changes as the semester progresses. Assignments will involve coding, answering multiple choice questions, written short answer questions, and mathematical proofs. More details on the assignments will be posted on the course webpage.
Corrections and Clarifications
We will make Piazza posts in the case of critical corrections. It is your responsibility to ensure that you are reading Piazza regularly.
Successfully Completing the Assignments
We have found through many years of teaching experience in various courses that the most common reason for poor homework performance is not starting early enough. Plan to do some work on the assignment every day and try to have it finished a few days ahead of the due date.
The second most common reason for not doing well on the projects is not asking for help when you need it. We offer help in office hours and on the class forums. When you come to office hours, please be ready to provide access to your code, e.g. via screen sharing. Another good way to get help is to post a question to the course forum. Remember, if you find that you are stuck on a piece of your project for an undue amount of time, please see us!
An important skill in programming is to be able to test and debug your programs independently. As such, we will not debug your programs for you. Instead, we will help you try to figure out how to test and debug your program yourself. We will also ask you to demonstrate what testing and debugging techniques you have already tried, and what the results were, before providing any advice.
Finally, some of the platforms that we use do not save your work in your browser or on a server. Even for those that do, we cannot absolutely guarantee that your code is saved or that the server does not crash. To be safe, please maintain a local copy of your work on your file system and update it regularly. If you somehow lose your work, it is your responsibility and extensions will not be provided.
Evaluation and Grading
Each homework assignment will be evaluated for correctness with respect to the instructions, and good programming practices, e.g. avoiding excessively complex solutions, or grossly unreadable formatting. In addition, some problems may also evaluate the quality of test cases that you supply.
It is not the case that a full score from the autograder means you solved the problem correctly! All code will ultimately be manually graded.
Due Dates
Assignments will be due at 11:59pm ET on the indicated due date. No late submissions will be accepted for any reason. If you have a medical or personal emergency, please contact the instructors as soon as possible. In all cases, we require written proof of the emergency. An excused assignment will be dropped and your remaining assignments increased in weight correspondingly.
Other than a medical or personal emergency, we do not excuse assignments for any reason. For example, we do not excuse assignments due to crowded computing sites, long office hour queue times, slow response times on the autograder, internet access problems, accidental erasure or loss of files, buggy software, or outside conflicting commitments (including job interviews, research conferences, and so on).
Regrade Requests
While we work hard to grade accurately, we sometimes make mistakes. If you believe we graded an assignment of yours incorrectly, you can submit a regrade request (via Gradescope) before the announced deadline for regrades for that assignment (typically 14 days after the grades are released). We reserve the right to regrade your entire assignment, which can cause your grade to go up, go down, or remain unchanged. Regrade requests should only be made if you believe a grading error has occurred, not if you are unsatisfied with the grading criteria or problem statement. Staff decisions on a regrade request are final.
Academic Integrity
You may give or receive help on any of the concepts covered in lecture, discussion, reading assignments, or textbooks. You are allowed to consult with other students in the class to help you understand problem specifications and definitions.
Unless otherwise stated, all assignments are to be solved individually. This means that no one should be watching you code, looking at your partial or complete solutions, or discussing solutions or possible solutions with you. You may not derive solutions from solutions found online for identical or similar problems. If you took this course in a prior semester or have been (dishonorably) given access to prior semester's solutions, you may not refer to or submit your own prior graded solutions or look at or base your solutions in any way on posted solutions if a similar or identical problem is included in this semester's assignments or exams. You may use small code snippets found in language documentation or other reference material but you must cite the source of the snippet in a code comment.
You may not use any automated system, e.g. an AI or natural language processing system, to generate solutions to assignments. You may use these systems to learn about the material and concepts covered in the course more generally. Any AI usage pertaining to an individual assignment's contents must be disclosed in your submission by attaching the relevant transcript to your submission.
You may not submit any code that attempts to subvert the grading system. The latter includes hard-coding solutions to discovered test cases, using run-time introspection to obtain information about private test cases, and so on. Code that violates these rules will summarily be given a zero.
To identify violations, we use both manual inspection and automated software to compare your solutions with each other and with prior submissions.
We reserve the right to report suspected violations to the Engineering Honor Council. The Honor Council will make final determinations about whether a violation of academic standards has occurred, as well as any sanctions. Read the Honor Code for detailed definitions of cheating, plagiarism, and other forms of academic misconduct.
Grading
The following table shows how each component of the course contributes to your overall score for the course:
| Assignments | 25% |
| Mid-Semester Exam | 25% |
| Course Project | 40% |
| Attendance and Participation | 10% |
The final course letter grade will be determined by the cutoffs given in the following table:
| A+ / A / A- | 97.5 / 92.5 / 90.0 |
| B+ / B / B- | 87.5 / 82.5 / 80.0 |
| C+ / C / C- | 77.5 / 72.5 / 70.0 |
| D+ / D / D- | 67.5 / 62.5 / 60.0 |
| E | 60.0 |
Our goal is to design assignments and exams so that a significant curve is not necessary. However, if based on the distribution of earned scores, we determine that a curve is necessary, the curve will only lower the cutoffs listed above. You can't be hurt by the curve.
Exam
We expect you to take the exam at the scheduled time. If you miss the exam and a medical or personal emergency is not involved, you will receive a zero for the exam. If you anticipate needing an accommodation for the exam, notify the instructors no later than 2 weeks prior to the exam.
Accommodations for Students with Disabilities
Some aspects of this course may be modified to facilitate your participation and progress. As soon as you make us aware of your needs, we can work with the Services for Students with Disabilities (SSD) office to help us determine appropriate academic accommodations. SSD (734-763-3000; http://ssd.umich.edu) typically recommends accommodations through a Verified Individualized Services and Accommodations (VISA) form. Any information you provide is private and confidential and will be treated as such. If you think you need an accommodation for a disability, please let your instructor know within the first three weeks of the term via the SSD office.
Commitment to Equal Opportunity
As indicated in the General Standards of Conduct for Engineering Students, we are committed to a policy of equal opportunity for all persons and do not discriminate on the basis of race, color, national origin, age, marital status, sex, sexual orientation, gender identity, gender expression, disability, religion, height, weight, or veteran status. Please feel free to contact any staff member with any problem, concern, or suggestion. All conversations will be kept confidential.
We ask that all students treat each other with kindness and respect, and try to be proactive in including one another, especially those who may not have an easy time making social connections.
Students' Mental Health and Well-Being
The university, and the course staff, are committed to helping to maintain the mental health and well-being of its students. If you or someone you know is feeling overwhelmed, depressed, or in need of support, consider the following university services:
- The CoE C.A.R.E. Center can help you understand your individual needs, help you navigate problem-solving options, and connect you to relevant resources. Online appointments can be made, and are confidential.
- For mental health concerns, contact Counseling and Psychological Services (CAPS) at (734) 764-8312 and https://caps.umich.edu during and after hours, on weekends and holidays, or through its counselors physically located in schools on both North and Central Campus.
- You may also consult University Health Service (UHS) at (734) 764-8320 and https://www.uhs.umich.edu/mentalhealthsvcs.
- For alcohol or drug concerns, see uhs.umich.edu/aodresources.
- For a listing of other mental health resources available on and off campus, visit http://umich.edu/~mhealth.
Research Disclosure
Your class work and logs of your interactions with tools might be used for research purposes in de-identified form (i.e. not attached to your name, uniqname, or any other individual identifier). For example, we may use de-identified student assignments to design algorithms or build tools to help programmers. Any student who wishes to opt out can contact the instructor at any time, up to one week after final grades have been issued and we will remove your data from all research datasets being collected, no questions asked. Opting out has no impact on your grade.
Research
Students interested in considering graduate or undergraduate research can make an appointment with the instructor to talk about potential research opportunities at Michigan. I am happy to discuss undergraduate or graduate advising, independent study projects, senior or Masters theses, research internships over the summer, research work for credit, graduate school applications, industry careers, and other topics beyond those covered in the course.
Right to Revise
The course staff reserve the right to make changes to the syllabus at any time as needed to better serve the course's needs. When a revision occurs, it will be announced on Canvas, and it is your responsibility to be informed of such.