Hi, I was having a look at the Golang Component ex...
# golangl
late-chef-72896
08/27/2024, 6:40 AMHi, I was having a look at the Golang Component example and noticed that besides registering resource outputs with
.RegisterResourceOutputst
thankful-flower-8175
08/27/2024, 6:52 AMI'm far from an authority but I'm working on a theory
thankful-flower-8175
08/27/2024, 6:53 AMhttps://go.dev/doc/faq#stack_or_heap
Perhaps there is a data dependency where these values must be kept alive
thankful-flower-8175
08/27/2024, 6:53 AMso they need to be stored somewhere so they are not considered stack local
thankful-flower-8175
08/27/2024, 6:53 AMbut I'm not sure why a copy wouldn't solve that issue. While you have it running locally what happens if you remove those?
l
late-chef-72896
08/27/2024, 6:54 AMI was thinking in the same direction. I'm going to do some testing
late-chef-72896
08/27/2024, 6:54 AMIt is just a bit confusing at the moment
t
thankful-flower-8175
08/27/2024, 6:55 AMI think it actually might just be the author of the example had a habit of returning things bundled (as if instead of a componenet this were a function to be called, and then the exports are done from the main.go)
thankful-flower-8175
08/27/2024, 6:56 AMand in fact if that were true then this component could be used as a regular import or a component in the manifest
thankful-flower-8175
08/27/2024, 6:56 AMso thats what I'm guessing
l
late-chef-72896
08/27/2024, 6:57 AMcould be indeed. thanks for your reply!
t
thankful-flower-8175
08/27/2024, 6:57 AMBut its worth nothing that I dont think that is clean (or works) because it still registers as a component resource and whatnot (but just because that is a useless operation doesn't mean it breaks things)
👍 1
9 Views