Difference between revisions of "Unsafe functions"
Jump to navigation
Jump to search
m |
|||
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"> |
||
⚫ | |||
− | |||
⚫ | |||
<tt>[https://discourse.haskell.org/t/using-unsafeperformio-safely/4146 Richard Eisenberg.]</tt> |
<tt>[https://discourse.haskell.org/t/using-unsafeperformio-safely/4146 Richard Eisenberg.]</tt> |
Latest revision as of 06:14, 11 August 2022
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 -> a
unsafeInterleaveIO :: IO a -> IO a
unsafeInterleaveST :: ST s a -> ST s a
unsafeIOToST :: IO a -> ST s a
unsafeIOToSTM :: IO a -> STM a
unsafeFreeze
,unsafeThaw
unsafeCoerce# :: a -> b
seq :: 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.