Andreas Rossberg
Andreas Rossberg
Ah, I was actually assuming that these would be copying operations analogous to `memory/table.init`. I guess it also makes sense to have versions that are fused with allocation, but those...
Well, true, but array.init is not in the proposal yet. :)
Mutual dependencies between sections are a reoccurring problem, esp wrt globals. Some might remember that that's also what caused us to introduce the `declare` segments for first-class references. As I...
> For this proposal I suggest we at least consider repeating the type section as the mechanism to denote recursion groups for iso-recursive typing. I thought about this, but turns...
I'm not sure I follow. What do you mean by "invoking a constant instance"? Can you give a code example? Just to be sure, just because some instruction _can be_...
@manoskouk, thanks for the example. I think I can answer that one quite easily: as far as the semantics is concerned, it's not `table.init` that triggers the evaluation of the...
@manoskouk, yes, fair point.
Yeah, throwing in a bunch of new sections just for this may not be the best way to go. We discussed allowing repeated sections on various occasions, and they are...
Yes, I agree that would have been a better design choice, but it's too late to do that without creating a mess now – global, table, memory, and element sections...
The current idea for supporting the combination of references and threads is that you can only share references across threads that are explicitly marked as sharable. That is, every reference...