The goal of this project is to give you experience in Hindley-Milner type checking.
We begin by introducing the grammar of our language which is based on the previous project with additional constructs. Then we will discuss the semantics of our language and type checking rules. Finally, we will go over a few examples and formalize the expected output.
1. Lexical Specification
Here is the list of tokens that your lexical analyzer should recognize (the new tokens are listed first):
2 Grammar
Here is the grammar for our input language:
3. Language Semantics
3.1. Types
The language has three built-in types: int, real, and bool.
3.2. Variables
Programmers can declare variables either explicitly or implicitly.
- Explicit variables are declared in an var_list of a var_decl.
- A variable is declared implicitly if it is not declared explicitly but it appears in the program body.
Example
Consider the following program written in our language:
This program has four variables declared: x , y , z , and w , with x and y explicitly declared and z and w implicitly declared.
3.3. Type System
Our language uses structural equivalence for checking type equivalence. Implicit types will be inferred from the usage (in a simplified form of Hindley-Milner type inference).
Here are all the type rules/constraints that your type checker will enforce (constraints are labeled for reference):
- C1: The left hand side of an assignment should have the same type as its right hand side.
- C2: The operands of a binary operator (GTEQ, PLUS, MINUS, MULT, DIV, GREATER, LESS , LTEQ , EQUAL and NOTEQUAL) should have the same type (it can be any type).
- C3: The operand of a unary operator (NOT) should be of type bool.
- C4: Condition of if and while statements should be of type bool.
- C5: The expression that follows the switch keyword in switch_stmt should be of type int.
- The type of expression binary_operator op1 op2 is the same as the type of op1 and
op2 if operator is PLUS, MINUS, MULT, or DIV. Note that op1 and op2 must have the
same type due to C2.
- The type of expression binary_operator op1 op2 is bool if operator is GREATER, LESS, GTEQ, LTEQ, EQUAL, or NOTEQUAL.
- The type of unary_operator op is bool.
- NUM constants are of type int.
- REALNUM constants are of type real.
- true and false values are of type bool.
4. Output
There are two scenarios:
- There is a type error in the input program
- There are no type errors in the input program
4.1. Type Error
If any of the type constraints (listed in the Type System section above) is violated in the input
program, then the output of your program should be:
Where <line_number> is replaced with the line number that the violation occurs and <constraint> should be replaced with the label of the violated type constraint (possible values are C1 through C5). Note that you can assume that anywhere a violation can occur it will be on a single line.
4.2. No Type Error
If there are no type errors in the input program, then you should output type information for all variables in the input program in the order they appear in the program. There are two cases:
If the type of the variable is determined to be one of the built-in types, then output one line in the following format:
where <variable> should be replaced by the variable name and <type> should be replaced by the type of the variable.
If the type of the variable could not be determined to be one of the built-in types, then you need to list all variables that have the same type as the target variable and mark all of them as printed (so
as to not print a separate entry for those later). You should output one line in the following format:
where <variable_list> is a comma-separated list of variables that have the same type in the order they appear in the program.
5. Examples
Given the following:
The output will be the following:
This is because the type of < b 2 is bool, but a is of type int which is a violation of C1.
Given the following:
The output will be the following:
This is because the type of b is int and the type of 2.5 is real which means in the expression + b 2.5, C2 is violated.
Given the following:
The output will be the following:
Given the following:
The output will be the following:
Note that b is not listed separately because it is marked as printed when listed with a on the first line of the output.
Given the following:
The output will be the following:
Given the following:
The output will be the following:
Given the following:
The output will be the following:
Given the following:
The output will be the following:
Given the following:
The output will be the following:
Note that z and w are not listed with x.
6. Requirements
Here are the requirements of this project:
- You should submit all your project files (source code [.cc] and headers[.h]) on Gradescope.
Do not zip them, and no need to submit on canvas anymore.
- This project expects inputbuf.h/cc lexer.h/cc parser.h/cc. If you use something else, please submit your own makefile named makefile in order to build your program.
- You should use C/C++, no other programming languages are allowed.
- You should test your code on Ubuntu Linux 19.04 or greater with gcc 4.9 or higher.
- You cannot use library methods for type checking, parsing or regular expression (regex) matching in projects. You will be implementing them yourself. If you have doubts about using a library method, please check it with the instructor or TA beforehand.
- You can write helper methods or have extra files, but they should have been written by you.
7. Evaluation
The submissions are evaluated based on the automated test cases on the Gradescope. Your grade will be proportional to the number of test cases passing. If your code does not compile on the submission website, you will not receive any points.
There will be three categories of test cases:
- Test cases with assignment statements (no if, while or switch ):
- Test cases with assignment, if and while statements (no switch ):
- Test cases with all types of statements
You can access the Gradescope through the left side bar in canvas.
