cps

In #193 we hid these so as not to annoy anyone. We should track them down and see if we cannot avoid them outright, and if not, why that is.

Track documentation from the point of novice and rewrite parts, which are hard to follow.
// And not forget about experienced developers' paths, who will not want to read 'Monad-101' intro for documentation on each library. Maybe write in addition a separate introduction to the library?

In that regard, the crate currently only supports:

#[with]
let ... = <call>?...?

as well as:

#[with]
let ... = match <call> { ... }
// rest *after* match (same scope)

which unsugar(s) to:

with_<call>(..., |__anon__| {
    let ... = match __anon__ { ... };
    // rest *after* match (same scope)
})

But it would be really nice i

In init.ts there are many almost copy paste of creating a new configuration. This should be harmonised.
e.g. https://github.com/INTO-CPS-Association/into-cps-application/blob/development/src/init.ts#L402-L432 and https://github.com/INTO-CPS-Association/into-cps-application/blob/development/src/init.ts#L371-L397