[Haskell-cafe] Enforcing coding policy (was: Why or why not haskell ?)

[Nils Anders Danielsson]

On Sun, 11 Dec 2005, Tomasz Zielonka <tomasz.zielonka at gmail.com> wrote:

> I would like to see some support in tools for enforcing such a coding
> policy. It could look like this - a function written using only safe
> components would be marked as safe. Every unsafe feature like FFI,
> unsafePerformIO, etc. would "taint" a module/function, marking it
> unsafe. You could explicitly tag module/function as trusted/reviewed/etc.
> There would be different levels of trust. All this would be propagated
> through the libs and program modules. A Haskell IDE could mark
> safe/unsafe/trusted code with different background color, etc. You could
> get statistics about the proportions of safe/unsafe/trusted code.

This sounds a lot like what they have been doing in the Programatica
project.

-- 
/NAD