H. S. Teoh
H. S. Teoh
Should we just close this then?
Maybe another approach that will speed up imports without massive mutilation of `std.uni` might be to generate `.di` file from `unicode_tables.d` and import that instead. That way, no actual code...
ping @wilzbach @DmitryOlshansky Any ideas how to move this forward?
ping @andralex Do the changes look OK now? Apparently this has stalled. Let's get it moving again!
This comes up every so often, the idea of mutating a container while iterating over it. The fact of the matter is, this will almost always lead to behaviour that...
Because of this, I recommend *not* explicating what happens with mutating a container while iterating over it -- rather, the user should be discouraged from doing this. The exact behaviour...
Changing the value in an AA is perfectly fine, obviously. What's _not_ OK is changing the key. The proposed change in this PR "officially" sanctions changing the current *key*, mentioning...
Also, note that mutating the key in an AA will cause bugs, because the hash value will not be updated, so the AA becomes internally inconsistent, and may start accepting...
+1, we definitely need to get this in. Security vulnerabilities are Not Good, both in the sense of security, and also from a marketing / PR perspective.
@timotheecour Sounds like that might be relevant for our little problem here. Can we at least try this out to see if it works? ping @CyberShadow