On the other hand having a filter construct is way nicer than having to manage the two arrays on your own.
Or worse yet, when someone is trying to remove items from a list that is self resizing, it is very easy to make bugs (by not adjusting the counter in the for loop when one is removed).
I understand that we get in a mess with different compilers not supporting the standard with cross platform code so MSVC should be changed.
But with respect to binding RValues to LValue references, why is the MSVC way not the standard? At first glance the MSVC way appears way more intuitive.
For instance if I have code:
update_X(X());
I would expect to be able to refactor it to this safely:
{
X x;
update_X(x);
}
The big catch is assuming that the team is big enough to put all the features into a variety of native apps.
It is possible that for a small team given the choice of one great web app or splitting time between Windows/OSx/iPhone/Android that the web app is superior.
At its face this looks like a good idea, but given the hassle of injecting the new checksum in the base file for every change I doubt it will be done by anyone but the most security conscious companies.
1. Not many people hand-write HTML tags these days, they tend to get generated at the level of apps like WordPress (which already has an SRI plugin) or frameworks like Rails (which can already do things like javascript_include_tag :application, integrity: true).
2. The people who do hand write HTML tags tend to be precisely the type of people who would go out of their way to generate an md5 checksum on the commandline, or write a script to post process their HTML files.