Programming Languages are the duct tape, bricks, mortar and steel of the information age. Over the last thirty years, a variety of languages with diverse features have been developed, expressive radically different perspectives of the idea of computation. CSE 162 is an introduction to these different perspectives, the fundamental concepts of languages, and how modern language techniques and idioms can be used to engineer software systems. For this purpose, we shall focus on three different paradigms -- functional, object-oriented and logic programming as embodied in OCaml, Racket/Rosette and Datalog.

Instructor: Yu Feng ([email protected])

TA: Yanju Chen ([email protected]), Yimeng Liu ([email protected])

Class: M,Wed, 9:30am, GIRV-2128

Discussion session: Friday, 9-9:50am, Phelp-3526

TA's office hour: Yimeng Liu (Mon, noon-2pm), Yanju Chen (Wed, 1pm-3pm)

TA Office: Trailer 936 Room 104

Instructor's office hour: Fri, 4pm-5pm, HFH-2157

Textbook (optional): Types and Programming Languages

1. Programming assignments: 50%

2. Midterm (Closed Book): 20%

3. Final (Closed Book): 25%

4. Class Participation: 5%

1. Racket: https://racket-lang.org/
2. The Rosette guide: https://docs.racket-lang.org/rosette-guide/index.html
3. More about Rosette: https://emina.github.io/rosette/
4. Serval tutorial: https://github.com/uw-unsat/serval-tutorial-sosp19
5. Hunter: https://fredfeng.github.io/Hunter/
6. Trinity: https://github.com/fredfeng/Trinity

• Cheating WILL be taken seriously. It is not fair toward honest students to take cheating lightly, nor is it fair to the cheater to let him/her go on thinking that cheating is a reasonable alternative in life.
• The following is not considered cheating:
  • discussing broad ideas about programming assignments in groups, without being at a computer (with code-writing and debugging done individually, later).
• The following is considered cheating:
  • discussing programming assignments with someone who has already completed the problem, or looking at their completed solution.
  • looking at anyone else’s solution
  • looking at solutions from the web, previous versions of the class, or anywhere else.
  • leaving your code (for example in an online repository) visible to others, leading others to look at your solution.
  • receiving, providing, or soliciting assistance from unauthorized sources during a test.
• Programming assignments are not intended to be grade-makers, but to prepare you for the tests, which are the grade-makers. Cheating on the programming assignment is not only unethical, but shows a fundamental misunderstanding of the purpose of these assignments.
• Penalties: If the teaching staff become aware of any violations of these rules by a student I will initiate the actions described in the Policy on Academic Integrity. If found responsible, the academic sanctions may result in a zero for the assignment, a zero for that portion of your grade, an “F” in the course, among others.