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.
> 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.
6.5.7. An object shall have its stored value accessed only by an lvalue expression that has one of
the following types:
- an aggregate or union type that includes one of the aforementioned types among its
members (including, recursively, a member of a subaggregate or contained union)
I see you use C macro templates. I have been experimenting with containers that use those. The advantages are speed and full type safety, and disadvantages are long compilations times (which have to be done only once though), the need to define a new template for every type in (only one) separate file, code bloat, and somewhat long function names (I don't use member function pointers).
A quick look shows this is storing void* pointers only. My excitement was quickly over as I was expecting something with _Generic macros or ability to manage memory for any type.
https://github.com/srdja/Collections-C/blob/master/src/hasht... shows the container is manually configurable. Look at the defines at the bottom. This would mean the container file source-header pair, would have to be duplicated for every type, which is somewhat manageable.
Any suggestions to fake the appearance? Think of distorting background images, for 2d video game purposes. And it doesn't have to be very accurate, just a general resemblance.
The eye went away. I wonder why.