High level concepts / patterns

[senier]

There are a couple of very helpful patterns like Typestate or Newtype which enhance robustness of the code.

I wonder how we should incorporate those high-level concepts. My current idea is:

• Identify useful patterns
• Reverse-engineer the rationale behind each pattern
• See whether those rationales
  (a) map onto an existing rule
  (b) justify an introduction of a new rule

In any case, we can potentially use those patterns as compliant examples or maybe as some non-normative addition.

Please share your thoughts on that.

[felix91gr]

I think it would make a lot of sense to have this in an Annex / Addendum in the document, where these kinds of patterns are explained and showcased. Then we might be able to point to them from Guidelines which suggest or otherwise ask the programmer to leverage them to help them comply.