Слава Україні! Героям слава!

@dbrattli I'm no expert, but it looks like this is how F# compiler (FCS) works for `[]` properties. In any case, it is not something that Fable is doing or...

@dbrattli @alfonsogarciacaro Looks like Dart also generates interfaces, so it has to be fixed there too (to not output `[]` properties in the interface).

As @alfonsogarciacaro said, most JS engines unfortunately have [not implemented TCO](https://kangax.github.io/compat-table/es6/#test-proper_tail_calls_(tail_call_optimisation)) yet. There are some JS workarounds that vary in performance, but Fable is not using any of them: -...

@TysonMN Trampolines may work but have some performance cost, which may or may not be acceptable to you. Yes, Fable is able to optimize (rewrite into a loop) some self-referencing...

I've wondered about that constructor naming too in the past, so it's a good idea to change it to make sense. I take it the change is just from `transformClassWithImplicitConstructor`...

@dbrattli Actually I take that all back, hopefully I'm not entirely wrong again ;) It's better to stick to the F# terminology, and there (like in other languages) the primary...

@dbrattli Yes, primary is another name for it, actually F# documentation doesn't really mention `implicit`, only `primary`, so that must be a .NET thing. We can switch to `transformClassWithPrimaryConstructor` then,...

@alfonsogarciacaro @dbrattli Fixed in #3061, feel free to merge if you approve.

@alfonsogarciacaro Do you see any difference compiling FCS-Fable itself? If not, then it could be some difference for certain F# constructs, in recent FCS package, perhaps you can try older...

@alfonsogarciacaro Can you use v40.0 for now?