You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Excerpt from @pmikkelsen's message:
A good idea is actually to pass something that isn't an array at all, and make sure we get the correct error. For example, 1+# should give an error. I have seen non-array arguments causing errors more than once.
In the interpreter, there are certain macros to check the rank of an array for example, and it is used like xxx->Rank. If some code is passed a namespace, the xxx->Rank will return garbage data, and likely cause a crash.
The text was updated successfully, but these errors were encountered:
Excerpt from @pmikkelsen's message:
A good idea is actually to pass something that isn't an array at all, and make sure we get the correct error. For example, 1+# should give an error. I have seen non-array arguments causing errors more than once.
In the interpreter, there are certain macros to check the rank of an array for example, and it is used like xxx->Rank. If some code is passed a namespace, the xxx->Rank will return garbage data, and likely cause a crash.
The text was updated successfully, but these errors were encountered: