Races in Fil-C allow access to one object through a pointer to a different object if there's an attacker-controlled offset involved.
Fil-C's safety guarantees therefore fail to apply in this situation.
Nonsense.
In a race, you at worst access an object you could have loaded from whatever field you were racing on.
In Go, you can bypass all protections and corrupt all of memory if you race on structs (I think).
Nonsense.
In a race, you at worst access an object you could have loaded from whatever field you were racing on.
In Go, you can bypass all protections and corrupt all of memory if you race on structs (I think).