Zoltán Lehóczky

These could be handled by "compiler intrinsics" of the Transformer specifically: instead of actually transforming them an efficient pre-created hardware implementation could be used (similarly how `ImmutableArray` support works). Maybe...

This would possibly not be an issue anymore with https://github.com/Lombiq/Hastlayer-SDK/issues/35

This is now covered for Vitis. Needs to test if `GenerateHardware()` can be completely decoupled from the `GenerateProxy()` method call, e.g. for offline use (it can be invoked but shouldn't...

> production could receive a different implementation that actually uses that technical name in a sanitized form What do you mean by this, exactly? Isn't the current implementation what production...

`AstNodeExtensions.GetFullName()` has a similar logic where it creates a globally unique (mostly human-readable) identifier for any node, even if it doesn't have an explicit name. Keep in mind that the...

Yep, I see. Was just referring to your second paragraph but on a second read, I was beside the point. `TransformedVhdlManifestBuilder.TransformMembers()` works in a parallelized way but `ConditionalExpressionsConvertingVisitor` and similar...

Following up here. Yep, we'd need to support those three scenarios indeed. `IReadOnlyList` should be fairly straightforward since we don't actually need to do anything with it on the hardware,...

Posit work ongoing in this repo, on this branch: https://github.com/Lombiq/Arithmetics/tree/issue/HAST-136

Since it's also a good thorough test of Hastlayer itself we've mostly completed it (the results including a lot of bugs fixed in Hastlayer, and support for method inlining added)....

The second one is a different issue. However, fixing CA1819 should rather be `ulong[] GetSegments() => _segments.Clone();` which would need specific support on top of that.