Pete Steinfeld

Most of these checks were already implemented and I just added references to them to the code and tests. I implemented the check for C747 to not allow coarray components...

When a derived type is declared in a separate module file, the function "evaluate::AttachDeclaration()" doesn't find the source provenance information for the base derived type. From what I can tell,...

TODO: Improve parsing error messages

3

Some erroneous sources produce messages that could do a better job of indicating what needs to be done to fix the problem. I've attached one such case. [parsequirk01.f90.txt](https://github.com/flang-compiler/f18/files/3167380/parsequirk01.f90.txt)

Current code uses parser::Messages and passes the source position parameter on every call to Say().

Scrub the compiler for uses of "enum" rather than "enum class"

3

I was trying to determine the type of a variable declared in a Fortran program. I had the declaration of type of the Fortran variable. Its declaration in the f18...

Implement validity checks for variable definition contexts

1

There are situations in a Fortran program which imply the modification of variables. These are known as “variable definition contexts”. Section 19.6.7 specifies 15 such contexts. One example is the...

The source code below produces a lot of messages that are not related to the actual source: ``` Program s3 integer :: i i = 3 volatile :: i end...

With the changes in pull request #612, there are now three visitors to do semantic checking for DO loops. We should see if we can reduce this number.

Check for PURE procedures containing image control statements

3

Constraint C1159 states that a PURE subprogram shall not contain an image control statement. This check can be modeled after a similar check for image control statements appearing in DO...

Implementing the code for this requires a way to go from a symbol with ```FinalProcDetails``` to the symbol for the associated procedure. The necessary infrastructure does not yet exist. I...