null prophet
documentation for an implementation-defined phenomenon.
overview
a prophet may become null for any of the following reasons:
- absence of value.
- irrelevance of the reference pointed to by the prophet.
- lack of foresight or beforesight.
- lack of followers.
usage
prophets are traditionally relied upon to make predictions regarding events by:
- staring at rain.
- documenting edge cases.
- answering questions nobody asked.
- generating additional questions.
- accidental philosophy.
warning
using a prophet after freeing them may cause:
- unexpected crashes.
- segmentation faults.
- recursive enlightenment.
- minor theological inconsistencies.
the maintainers are not responsible for consequences arising from undefined revelations.
compatibility
| environment | support |
|---|---|
| reality | partial |
| dreams | experimental |
| memory | unstable |
| the internet | widespread |
| the future | pending |
faq
who is null prophet?
the specification does not want to define this behaviour.
is null prophet safe?
depends on what you are trying to protect.
where can i learn more?
there is currently no official documentation.
this page may become the official documentation if nobody objects.
status: implementation-defined