Change Safe-Haskell status of `System.IO` to `Trustworthy`

[jeltsch]

System.IO has Safe as its Safe-Haskell status, which is possible because the implementation of System.IO is in GHC.Internal.System.IO. However, there is GHC merge request !15694, which seeks to move most of the System.IO implementation into System.IO itself and thus from ghc-internal into base. This move necessitates changing the Safe-Haskell status of System.IO to Trustworthy, a change that said merge request already includes.

I propose to go forward with this change of Safe-Haskell status. Note that the above-mentioned merge request does not change the trusted codebase in any way; it just moves part of it into a different place.

[TeofilC]

I think this is somewhat uncontroversial, so I'll wait a few days (for any questions) and then trigger the vote.

[ChickenProp]

To clarify (correct me if I'm wrong): this increases the number of Trustworthy modules, because GHC.Internal.System.IO still exists, defining just print and putStrLn. But System.IO was previously nothing but re-exports, so the amount of code in Trustworthy modules stays the same.

So if someone wants to check everything in every Trustworthy module, I think this doesn't make things harder for them.

(e: I guess this is basically what you were saying with "Note that the above-mentioned merge request does not change the trusted codebase in any way; it just moves part of it into a different place.")

[jeltsch]

That’s correct, @ChickenProp.

[TeofilC]

Let's vote @velveteer @Daniel-Diaz @ChickenProp @noughtmare @mpscholten @doyougnu @parsonsmatt @jeltsch @rickowens

+1 from me

[mpscholten]

+1

[jeltsch]

+1

[ChickenProp]

+1

[rickowens]

+1

[doyougnu]

+1

[Daniel-Diaz]

+1

[noughtmare]

+1

[velveteer]

+1

[TeofilC]

Thanks folks! With 9 votes in favour, this proposal is accepted.