Fields initialization

after targeting C#, all fields initializations are moved into class's constuctor, and puts after calling constructor of super class. In most of all cases it;s fine, but here is onle example, that will not work:
`class b {}`
`class a extends b {public var test:Int = 1;}`
If class b represents some kind of deserializator (from json-type string, for example), it will initialize some fields, implemented in class a, using reflection.
so:
1) constructor of class 'a' calls constroctor of class 'b'
2) class 'b' deserializes data, and initializes field 'test' of class 'a'
3) class 'a' replases data from field 'test' with default '1';

Start with the C# target's generated-constructor and field-initialization handling, then reproduce the issue with the class a and class b example in the report. Trace the order of superclass construction, deserialization, and default field initialization; done means the inherited deserialization value is not overwritten by the subclass default.

Written by the indexing model from the issue text.