Refactor to DisplayClass handling not to be a special case (HAST-253)
Piedone opened this issue · comments
Currently, DisplayClasses and how they are used are handled as a special case due to them being generated for multi-threaded code. However, now that we have OOP support, we could remove this specialized behavior and instead handle DisplayClasses as any other class.
For this, we'd need to support fields apart from properties as class members too, which is done now.