On 5/2/12 12:20 AM, Jakob Ovrum wrote:
S(...) does not exhibit the same problem as {...} exactly because it has
constructors and static opCall. If you change the order of fields in S,
you can write a constructor preserving the old behaviour.
Good observation. So indeed the { ... } case is inferior because there's no reasonable way for the library writer to defend against.
Andrei
