It is very sensible that since v0.6, the BaseObject intrinsic is always loaded. However, in a custom setup, the BaseObject intrinsic is loaded after the custom intrinsics, which means all the custom intrinsics cannot assume BaseObject. If BaseObject is added to the list of custom intrinsics, BaseObject gets loaded twice, which causes a SIGABORT.
Additionally, All still contains Base, which similarly causes SIGABORT.
This PR loads Basebefore the custom intrinsics. It also removes Base from All (and adds some tests for this).
DelSkayn
commented
2 months ago
It is very sensible that since v0.6, the
BaseObjectintrinsic is always loaded. However, in a custom setup, theBaseObjectintrinsic is loaded after the custom intrinsics, which means all the custom intrinsics cannot assumeBaseObject. IfBaseObjectis added to the list of custom intrinsics,BaseObjectgets loaded twice, which causes a SIGABORT.Additionally,
Allstill containsBase, which similarly causesSIGABORT.This PR loads
Basebefore the custom intrinsics. It also removesBasefromAll(and adds some tests for this).