Allow homogeneous tuples as function arguments

[EmilyBourne]

Allow 1D homogeneous tuples as function arguments. Fixes #738. Homogeneous tuples as arguments already worked in the low level code as homogeneous tuples are handled as arrays, however the wrapper was missing which meant that such functions couldn't be called from Python. In order to handle multi-level tuples some reorganisation of the wrapper was necessary. Namely the introduction of the _extract_X_FunctionDefArgument functions. However Python multi-level tuples may have different lengths in the elements. It proved difficult to check the size of the elements in a generic way so this was left for later work (the obvious solution is to use lists to support this).

Commit Summary

• Update docs
• Update BindCFunctionDefArgument to handle tuples as strideless arrays
• Add descriptions of more tuple functions from Python.h. Group these functions together in ast.cwrapper
• Make dtype a searchable attribute of SyntacticTypeAnnotation
• Fix filter for used template type annotations so it also searches through indexed elements to find objects in a tuple annotation.
• Add tests for tuples as arguments
• Rename _get_check_function->_get_type_check_condition.
• Allow _get_type_check_condition to return a condition which is not a function call (e.g. a Variable)
• Add body argument to _get_type_check_condition to allow additional commands to be run before determining if the type is correct.
• Add type checks for homogeneous tuples
• Introduce _extract_X_FunctionDefArgument functions to describe container unpacking recursively
• Add _extract_HomogeneousTupleType_FunctionDefArgument function to unpack 1D homogeneous tuples.
• Ensure errors are raised for multi-D tuples.

[pyccel-bot]

Hello again! Thank you for this new pull request 🤩.

Please begin by requesting your checklist using the command /bot checklist

[EmilyBourne]

Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:

• Write a clear PR description
• Add tests to check your code works as expected
• Update documentation if necessary
• Update Changelog
• Ensure any relevant issues are linked
• Ensure new tests are passing

[EmilyBourne]

/bot run docs

[EmilyBourne]

/bot run pylint pyccel_lint spelling docs

[EmilyBourne]

/bot run pylint

[pyccel-bot]

It seems like you have forgotten to complete your checklist for this pull request. Please check the list here, fix the missing items and let me know when everything is ticked and fixed with /bot mark as ready.

[pyccel-bot]

Unfortunately your PR is not passing the tests so it is not quite ready for review yet. Let me know when it is fixed with /bot mark as ready.

[pyccel-bot]

Good job ! Your PR is using all the code it added/changed.

[pyccel-bot]

Hey @pyccel/pyccel-dev ! @EmilyBourne has just created this great new pull request! Check it out and let me know what you think!

[mustapha-belbiad]

Looks Good to me.

[pyccel-bot]

Good job ! Your PR is using all the code it added/changed.

[pyccel-bot]

Hey @yguclu, @EmilyBourne, this PR is looking pretty good. @EmilyBourne and @mustapha-belbiad think it is ready to merge. Could you add your expertise to confirm that this follows all the coding conventions and fits in Pyccel's future plans? Thanks 😄