Sergi Siso

Since I am introducing the `node.debug_string()` for error messages which takes care of avoiding the deep_copy issue and replacing the FortranWriter in error messages with this new functionality I think...

Ok, so no need to close the issue. At least now there is a single point where this configuration decision can take place (inside the debug_string() method), before the Writers...

The PR that introduces this feature has been merged, but it would be good to update the Wiki "New release" page before closing the issue. @arporter Could you update the...

@ZedThree We merged the block and critical construct support PR. Can this be closed now?

@TeranIvy this is how we solved the PSyclone tests using the FAKE_METADATA_KERNEL variable in `src/psyclone/test/psyGen_test.py` but because fparser1 was accepting the input I decided to create the issue anyway. If...

@hiker @arporter and the Codecov status check is working again 🥳 (after we reinstalled the github app). I will close the codecov issue now.

Note that Fortran 2018 has a `block-specification-part` with only the supported subconstructs instead of a constrain, which make it easier for parsing.

Thanks @hiker , Sebastien had this problem in psyclone and I didn't realize it was a Fortran format issue. Can the format for the psyclone cli input file be changed?...

Couldn't we simply avoid matching Structure_Constructors? We would still be wrong (as not returning what the standard says it is - now we do the same just the other way...

I created #449 to test this. Note that this does not attempt to solve the conflict with PartRef also mentioned in the original comment, only the Structure_Constructor.