Alistair Pirrie

I've addrsesed all the open comments. It's possible I've been a little overzealous with the changes from array to ScalarArray, so just let me know. Otherwise, this is ready for...

I've added some documentation for the subroutine call. The design in #1312 seems to suggest that the ScalarArray is only variable needed in the subroutine definition, so hopefully this is...

This still isn't working as intended, but is getting closer to correct. As an example, the code gen is now adding the scalar arrays to the generated code, alongside the...

I'm unsure how to add the declarations correctly. The ScalarArray needs to have `dimension(dims_array(1), dims_array(2), ... )`. I've tried creating each of `dims_array(n)` as individual symbols which get added to...

Ah I see, I wasn't aware you could create an array like that - I'll give that a go, thanks!

This is getting closer to being correct. Currently it's adding the dimension of `dims_array` wrong (e.g., as `dimension(1,1,1,1)` instead of `dimension(4)`). I've added it this way as a temporary fix...

I've managed to break some of the other tests too - I suspect this is because of some unintended changes to normal scalar values. I will investigate

This is definitely a step in the right direction. I have managed to add ArrayReferences to the dimensions array. The current code generation is creating the following - `integer(kind=i_def), intent(inout)...

The current failure is a bit strange, I haven't touched `testkern_type` explicitly so I'm a bit confused why it's got the wrong number of arguments all of a sudden. I'll...

This is now generating code and the stub for my written tests. The code gen looks sensible, the stub gen needs more work. I haven't managed to fix the error...