dispatch_barrier_async can lead to inconsistent values when using mutable objects

首先在启用和禁用模拟器性能的情况下重现已报告的 registerDefaults 和 setObject:forKey: 场景，然后跟踪 dispatch_barrier_async 的处理。完成标准是：突变始终遵循 NSUserDefaults 的行为，而不是依赖屏障时序或性能模式。

dispatch_barrier_async works great for this project, except for the following situation:

1. NSMutableDictionary *registeredDefaults = [[NSMutableDictionary alloc] init];
2. [[NSUserDefaults standardUserDefaults] registerDefaults:registeredDefaults];
3. [registeredDefaults setObject:@"FOO" forKey:@"BAR"];
4. NSObject *value = [[NSUserDefaults standardUserDefaults] objectForKey:@"BAR"];

• With sim performance ON, value may be equal to nil or equal to @"FOO" depending on if line 3 executed before the internal barrier_async block executed.
• With sim performance OFF, value is always equal to nil. Mutations after line 2 are not acknowledged.

The code above is incorrect anyways (you wouldn't expect it to work) -- but we still need to honor the behavior of NSUserDefaults. You could emulate this bug using -setObject:forKey: with a mutable object.