Joe Eli McIlvain

Right, that matches my understanding. And if that's true, then this is not a safety issue, in my opinion. Though if Sean has something else to add for consideration, that's...

> I could disallow FFI to a 3rd party module and it could still use cpointer with an offset to get access to arbitrary memory to attempt to use in...

I mentioned this to Sean in a DM conversation just now, but for the record here: I'd be okay with removing all forms of pure-Pony pointer offset math, as long...

At any rate, I do want to change the title of this ticket a bit to make it more accurate - so far I think we don't know of any...

We discussed this during sync - the next step would be to use a debugger like lldb to catch the assert fail and figure out what code path is calling...

@stefandd - We already have the `opt` here in this scope (it's the last parameter received by `add_special`) so in my opinion there's no reason to pass `NULL` to `lookup_try`...

As to the question of how it's not currently crashing the compiler, I don't know and couldn't say further on that without some investigation.

I notice that the tests didn't pass for musl.

@dimiii - Building a Pony compiler in Pony is a long-term goal, though it represents a major amount of work. There are no plans to write the runtime in Pony,...

@peterzandbergen - it definitely still needs to be fixed, and it's still marked as high priority. Runtime segmentation faults are not acceptable .