Adrian Cole
Adrian Cole
@rogeralsing that's one way to implement such a feature. Another would be to make a top-level field. A top-level field would likely be more efficient and also open up the...
Thanks for raising this issue, the status quo is quite not ergonomic. It would really be best for everyone to separate desire to push component model technology from it also...
unsolicited 2p is to make sure you get folks who are fulltime in Go on the design review as there are some notable cultural differences between it and rust, especially...
In hindsight, I phrased things poorly. I should have said something like... This issue is an example of people recognizing areas of improvement on TinyGo. For example, it was mentioned...
Since asked, here's what I think could be improved beyond what's already noticed. As the contributor to dapr is a WASI lead, I didn't split hairs. Maybe I should have...
one last thing is that tinygo is actually maintained by people who have stake in wasmtime. Literally, `tinygo test` uses wasmtime by default. This may not be well known, but...
I misunderstood things and really sounds like I'm not providing helpful feedback. I prefer not to go round-and-round, rather call it a day. Good luck and hope some of what...
yes! for starters non-componentized is great. meanwhile I was thinking to emit c and then wasm2wat the result ;)
I think this is very important especially as modeling is fluid here. For example, it isn't intuitive that 64bit flag would be two fields, especially as wasm supports 64 bit...
@Maaarcocr I'm cool on your view of the outcome