Do they expect us to believe that the parts will be reused, like it is implied in the video? Of course not, there is not chance the parts will match the next model and even if they do they would have to undergo inspection and testing. That is way to expensive and time consuming. Instead they will be melted into raw components, which is not shown in the video.
What will happen in reality is the phone will go into a industrial shredder and then the process of separating/recycling will begin. The robot seems like a marketing gimmick (they even have it a name), and will not be involved in 99% of the recycling process.
They talk about harvesting the raw metals and elements in the video... The hard part in ewaste recycling isn't collecting the devices, it's breaking them down into their isolated components. The robot's aim is to do that instead of a shredder so that they can have a much higher re-use rate.
> But that type of action is extremely rare and isn't likely to happen here.
Given the importance of the situation it seems it is very likely it is going to happen just here. It's up to the judge(s).
>and family court judges aren't overly likely to go along with that.
It's up to the judge(s).
>The FBI could potentially convince a psychiatrist...
This is just redirecting pressure to a different person, keep doing it until you find that someone who will buckle.
> Most members of the law enforcement community are decent people and aren't willing to do that type of stuff.
Just like above, most are honest, but you only need one that isn't.
If you think all of those are impossible by the US government, take a look at you know where, where torture doesn't happen, and no-one was prosecuted for torture that didn't happen.
>
Just make a fast allocator that uses heap instead of the stack. You only need to malloc once and it can be used for any type since like you pointed out, it's effective type can be changed.
Sometimes, especially in embedded systems, it is useful to have a bunch of statically allocated heaps. You can see them in a memory map, and the linker will tell you if they don't fit in memory.
There is also the case where you have some raw data from a file or network, that you want to re-interpret as a struct. That is always dangerous with endianness and struct padding, but it is a very common practice. You could always memcpy from a char array to a struct, but that can waste memory.
"More importantly, they allocate a data-dependent amount of stack space that can trigger difficult-to-find memory overwriting bugs: "It ran fine on my machine, but dies mysteriously in production"."
The eye went away. I wonder why.