Difference between revisions of "Unsafe functions"
Jump to navigation
Jump to search
m |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div style="border-left:1px solid lightgray; padding: 1em" alt="blockquote"> |
<div style="border-left:1px solid lightgray; padding: 1em" alt="blockquote"> |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| − | |||
| ⚫ | |||
</div> |
</div> |
||
Latest revision as of 12:27, 8 June 2023
A colleague [...] asked me today whether I know how to use unsafePerformIO safely. And I realized I have no idea. [...]
There are a number of unsafe functions in the libraries.
unsafePerformIO :: IO a -> aunsafeInterleaveIO :: IO a -> IO aunsafeInterleaveST :: ST s a -> ST s aunsafeIOToST :: IO a -> ST s aunsafeIOToSTM :: IO a -> STM aunsafeFreeze,unsafeThawunsafeCoerce# :: a -> bseq :: a -> b -> b
Unsafe functions can break:
- type safety (
unsafeCoerce#,unsafePerformIO),
- equational reasoning (
unsafeInterleaveIO),
- or parametricity (
seq).
Their use (except in the case of seq) would require some
kind of assurance on the part of the programmer that what they're doing
is safe.
unsafe is also a keyword which can be used in a foreign import declaration.
This article is a stub. You can help by expanding it.