Fix for error in lambda for tracking collisions + safe external lambda errors. #3136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds UnsafeExtCall and ExtCall functions to the lambda type.
(UnsafeExtCall is "Unsafe" because it doesn't check args, it mimicks UnsafeCall)
These will pcall the lambda function and instead of throwing (which will trigger a lua error) will instead return nil and error the E2 chip.
Fixes collisions no longer being tracked after having an error occur in the lambda's callback, now properly produces errors on chip.