Action_27: No coding guideline for RUST exists. Coding standards need to be defined.

Guideline should cover:
- Enforcement of low complexity
- Use of language subsets
- Exclusion of ambiguously-defined language constructs which may be interpreted differently by different modellers, programmes, code generators or compilers
- Exclusion of language constructs which from experience easily lead to mistake, for example assignments in conditions or identical naming of local or global variables
- Exclusion of language constructs which could result in unhandled run-time errors
- Enforcement of strong typing
- Use of defensive implementation techniques. Examples:
- Verify the divisor before a division operation (different from zero or in a specific range)
- Check an identifier passed by parameter to verify that the calling function is the intended caller.
- Use the "default" in switch cases to detect an error
- Use of well-trusted design principles
- Use of unambiguous graphical representation
- Use of style guides
- Use of naming conventions
- Concurrency aspects

#1146