Juraj Kirchheim

Silly question: why should it even fail at compile time? I think it should try to perform the assignment at runtime and thus behavior according to whatever the runtime semantics...

Since adding optional fields always incurs a marginal risk for breaking user code, might I use this opportunity to request also adding the positions of other names currently not exposed?...

Random idea: `A`.

Seems to be cutting very close to the proposed [`@:displayName`](https://github.com/HaxeFoundation/haxe/issues/8742#issuecomment-534680677). Also, `@:message.follow` or even `@:message.message` seems an odd description for that `EitherType` use case. What's desired in both cases is...

> I don't want to add random shorthands for `EitherType` _unless_ we decide to actually support `|` in syntax. The problem with that is that I'm not sure it should...

Stupid question: why exactly does the typing of `Main.B` involve the typing of `Main.A`? Because as it is, there is nothing cyclic in the code. It's not like the build...

Generally, having the build of one class depend on the structure of another is very useful. It's what [syntactic delegation](https://haxetink.github.io/tink_lang/#/declaration-sugar/syntactic-delegation) works in tink_lang. And it's how one would have to...

FWIW I found my way around this. But I'm personally still a bit worried/puzzled by "Trying to type things while in a build macro is unsound." although I haven't fully...

When in a build macro, try to avoid triggering expression typing. For example, you might be able to generate macro calls in the returned fields, that will get run later,...

Hmm, dunno. The status is that the commit I linked introduced a regression. I suppose there are good reasons, but it's not exactly transparent why this restriction got added or...