Who benefits from the `indirect` keyword?

[LucianoPAlmeida (Luciano Almeida)]

@Lantua

The layout would be 1 Int + 1 Array. IIRC Array has its own heap-allocated storage under the hood (with a few metadata), so Recursive ends up having finite size (with the next entry floating somewhere else in the heap memory).

That's kinda what I was expecting. Thank you @Lantua :)

@Lantua

Makes me thing we may want to have indirect inside struct , which would most definitely do different from enum, but achieve the same effect on memory footprint.

Do you mean something like

struct Recursive {
  var value: Int
  indirect var next: Recursive?
}

?

I think this would make sense as you said.