Skip to content

doc: CLOS is safe sometimes #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
iskamag wants to merge 1 commit into from
Closed

doc: CLOS is safe sometimes #222

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/internals/supervisor-restrictions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Writing code that runs as part of the supervisor comes with a few restrictions, particularly code that runs early or as part of an interrupt handler. This is a non-exhaustive list of restrictions.

General restrictions:
* No classes or methods. defclass/defmethod/defgeneric and the clos implementation in general are not written in a supervisor-safe way. Use structures and pass functions around instead.
* with small exceptions, No classes or methods. defclass/defmethod/defgeneric and the clos implementation in general are not written in a supervisor-safe way. Use structures and pass functions around instead, or ensure the code is wired and fully warmed-up.
* Restrictions on allocation. Depending on what kind of supervisor code you are writing, you may need to consider what allocation area is used to allocate from. If the code accessing the allocated object may be called during GC or an interrupt handler the object must be allocated from the wired area. For example, global variables accessed from interrupt handlers must be defined with defglobal, not defvar. Defining them with defvar will result in rare crashes.
* Restrictions on memory access. Depending on the context the code is called from (during a GC, for example), it may not be possible to access non-wired memory.

Expand Down
Loading