[{"name":"Unsafe","comment":" Unsafe functions that CRASH when called.\n\n\n# DO NOT USE!\n\nReally. It's for educational purposes. So go ahead and read the source and meditate on it. Don't use it.\n\n\n### How to use\n\nOK OK. There is only one legitimate use case: when you have a logical proof that calling a function is impossible.\n\n\n### Which one to use\n\nDo you have a logical proof? If not, use Maybe.\n\n\n## Crash!\n\n@docs infiniteLoop, stackOverflow, exception\n\n","unions":[],"aliases":[],"values":[{"name":"exception","comment":" Throws a javascript exception immediately.\n\nThis is achieved by comparing two functions.\n\nThe error is even more cryptic than `stackOverflow`, but the CPU, memory and interactivity are not stressed.\n\nThrows the following exception:\n\n```text\nError: Trying to use `(==)` on functions.\nThere is no way to know if functions are \"the same\" in the Elm sense.\nRead more about this at https://package.elm-lang.org/packages/elm/core/latest/Basics#== which describes why it is this way and what the better version will look like.\n```\n\n","type":"a -> b"},{"name":"infiniteLoop","comment":" Go into an infinite loop.\n\nThe browser tab will become unresponsive. CPU use will increase, potentially impacting machine usability and battery life.\nBecause of Tail Call Optimization, the stack will not overflow, instead the browser will show a button to reload the tab after a timeout.\n\n","type":"a -> b"},{"name":"stackOverflow","comment":" Create a stack overflow which throws a javascript exception.\n\nBriefly uses a lot of CPU and memory so interactivity suffers. You should use `exception` instead.\n\nThrows the following exception:\n\n```text\nInternal Error: Too much recursion\n```\n\n","type":"a -> b"}],"binops":[]}]