Open TethysSvensson opened 2 years ago
I think is a general flatbuffers problem -- it does not make sense for a FB struct to be self-referential since they don't support references and would be infinite size. This should have been rejected by the flatc Parser before it got to the Rust code generator. I'd imagine this bug can be replicated in C and possibly elsewhere.
@aardappel
Yup, the parser should error on this.
This issue is stale because it has been open 6 months with no activity. Please comment or label not-stale
, or this will be closed in 14 days.
I don't think this has been fixed.
This issue is stale because it has been open 6 months with no activity. Please comment or label not-stale
, or this will be closed in 14 days.
I still don't think this has been fixed.
This issue is stale because it has been open 6 months with no activity. Please comment or label not-stale
, or this will be closed in 14 days.
This will still segfault on current master.
This issue is stale because it has been open 6 months with no activity. Please comment or label not-stale
, or this will be closed in 14 days.
Nothing has changed, this still causes a segfault in safe rust on current master.
If you make a self-referential structs in flatbuffers, it still compiles, but outputs invalid code:
This code will print the content of the stack and then segfault using only safe rust.