Agent functions conditions in native python

[mondus]

Fixes #909

Requires the following

• Support within the code generator
• Unit testing in the code generator
• Integration test
• Documentation PR (Updated docs for agent function conditions FLAMEGPU2-docs#112)

[Robadob]

As mentioned in meeting, AgentFunctionCondition's don't have access to any setters (any methods that can change state). Their API object is instead ReadOnlyDeviceAPI

It doesn't look like there's anything to handle this gracefully, or is the plan to leave users at the whim of C++ errors (I'm not sure how bad they would be, probably just method x does not exist).

[mondus]

As mentioned in meeting, AgentFunctionCondition's don't have access to any setters (any methods that can change state). Their API object is instead ReadOnlyDeviceAPI

It doesn't look like there's anything to handle this gracefully, or is the plan to leave users at the whim of C++ errors (I'm not sure how bad they would be, probably just method x does not exist).

The code generator will not distinguish between the Device API or Read only API. It will just check against a list of API functions so will raise compilation errors if a user tries to set a variable. It is not a "proper" static analyser as it is a tree walker that doesn't retain state so there are other examples where people may call functions out of context that would raise compilation errors. E.g. You can call wrapped message functions on not wrapped implementations.

The overall ambition of the code generator is to translate correct code (and filter out anything obviously wrong) but it is not expected to catch all errors that a compiler would. This would be done via Jitify 2 when we could link compile errors back to python code lines.