From dca6752fecc6733575145185764d7b6a218cee96 Mon Sep 17 00:00:00 2001 From: Koichi Sasada Date: Mon, 21 Dec 2020 18:06:28 +0900 Subject: Introduce Ractor::IsolationError Ractor has several restrictions to keep each ractor being isolated and some operation such as `CONST="foo"` in non-main ractor raises an exception. This kind of operation raises an error but there is confusion (some code raises RuntimeError and some code raises NameError). To make clear we introduce Ractor::IsolationError which is raised when the isolation between ractors is violated. --- vm_core.h | 1 + 1 file changed, 1 insertion(+) (limited to 'vm_core.h') diff --git a/vm_core.h b/vm_core.h index 8540f8d1de..453c84e394 100644 --- a/vm_core.h +++ b/vm_core.h @@ -2011,6 +2011,7 @@ extern void rb_reset_coverages(void); void rb_postponed_job_flush(rb_vm_t *vm); extern VALUE rb_eRactorUnsafeError; // ractor.c +extern VALUE rb_eRactorIsolationError; RUBY_SYMBOL_EXPORT_END -- cgit v1.2.3