In general, no: most duplicates stay around. Having multiple copies of the same question with different wording is useful as search fodder, because people looking for an answer may use different wording too.
That's good to see that they actually have the right rules, but I've used it many times where my questions were closed simply for appearing similar to others (when I did not even find the others in my search results). I suppose the mods can be overzealous.
I think this highlights that while there are easy solutions to the problem the OP faced, they're difficult for a newcomer to discover. (I have been using Rust for a couple of months and I'd also have reached for serde and maybe serde_derive to solve the problem).
Hopefully this is something the Libz Blitz[0] will solve with their Rust Cookbook[1]. (You could almost but not quite arrive at as simple a solution from chapters 1 and 2).
I think the key part is "regardless of where they come from". For instance, Scotland has free tuition for the Scottish and other EU citizens, but not for citizens of England/Wales/NI or international students. (The fees for an English person are typically cheaper than other English universities, but still not to be sniffed at).
I am not sure about NI or Wales, but I imagine there's a similar situation.
The firmware signature ensures the updates are authentic, but not that they are fresh. An attacker could force devices to stay on an older authentic but vulnerable piece of software.
I think plain HTTP is not appropriate for most update schemes Interestingly, Google Omaha actually chose not to use TLS to ensure freshness, but has something custom.
An attacker could just as easily block the SSL connections - unless you're suggesting it fail if it can't check for a firmware update, but that proposal would mean that if your servers are gone the devices are bricked. Many of such devices function fine in a Lan only setting behind a nat where they're virtually untouchable.
Disallowing downgrades via a signed datestamp is about the best you can do. Anything else will either be trivially blocked or result in other user problems.
Arguably someone adhering to the C++ Core Guidelines, using GSL and using the new static analysis tools (currently only in VS?) can be reasonably confident about choosing C++ for a new project in 2017.
I suspect this is because Theresa May didn't want the UK policy to be so blatantly discriminatory, but still wanted to obsequiously support Donald Trump in the hopes of receiving preferential treatment from America as the UK severs its ties with other EU member states.
Whatever the intelligence says about the risk of certain devices, I can't see how that threat doesn't apply equally to passengers travelling from any country (although plausibly there could be significantly increased risks relating to passengers of certain nationalities).
This policy feels like an obvious target for someone to crowd-fund a judicial review into.
The new content looks a lot better, but I think it is a shame that this is not using the "MSDN" branding. One of the nicest things about Microsoft documentation is that I can add the term "MSDN" to any random web search and usually get the page I'm after.
Fantastic. Maybe hide the word "MSDN" somewhere in the page, just for search engines. Old habits die hard. :)
Slightly off-topic, but would it be possible to reinstate the code samples on the IIS Native Module section[0]? It seemed to go walkies about a year ago and no amount of "Is this page helpful?" feedback seems to get it back. It's quite important because there is little documentation elsewhere on the internet.
Could you provide an example where the borrowing would cause issues for immutable data?
I'm still learning Rust, but I thought the fact that you could have as many immutable borrows as possible would limit what errors the borrow checker could throw at you.
I do find the image of "fighting the borrow checker" is quite harmful to how people view Rust. As those links state, an important aspect of teaching Rust is educating people about why the borrow checker complains, so that they might adjust their mental model.
