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
I don't know if it's possible to build a fence around the underlying problem that kept #143 from being accepted, but I just ran into it, or something that looks like it, while attempting to return an array of structures.
See the example. Basically, I looked at the documentation and did the obvious for SomeStruct and Element, and ended up with a segfault generating machine.
Assuming that the underlying problem that causes a segfault in PyFinalizeEx can't be fixed, it would be nice if the documentation for Element had some verbiage along the lines of "don't do this, you'll be sorry". Better, if it's achievable, would be a way to generate a build-time fault if you try.
I don't know if it's possible to build a fence around the underlying problem that kept #143 from being accepted, but I just ran into it, or something that looks like it, while attempting to return an array of structures.
See the example. Basically, I looked at the documentation and did the obvious for
SomeStruct
andElement
, and ended up with a segfault generating machine.Assuming that the underlying problem that causes a segfault in
PyFinalizeEx
can't be fixed, it would be nice if the documentation forElement
had some verbiage along the lines of "don't do this, you'll be sorry". Better, if it's achievable, would be a way to generate a build-time fault if you try.Reproducible example:
example.zip
The text was updated successfully, but these errors were encountered: