On Thu, Aug 19, 2021 at 7:30 PM rmfr <remus.clearwa...@gmail.com> wrote:
>
> Thanks a lot, Ian :-)
>
> > Assuming you are running on an ELF system and control symbol
> visibility, this can work.
> > To be clear, this is not supported by the Go project.
>
> Do you mean that this usage is not recommended in a production environment?
> And this usage maybe no longer supported by Golang runtime in future updates?

I mean that while it may accidentally happen to work today, it may
break in future releases.  If it does break, we will not fix it to
work again.  You should not assume that this will continue to behave
in the future as it behaves today.

Ian



> On Friday, August 20, 2021 at 3:19:22 AM UTC+8 Ian Lance Taylor wrote:
>>
>> On Thu, Aug 19, 2021 at 6:34 AM rmfr <remus.cl...@gmail.com> wrote:
>> >
>> > As the title describes, does this is allowed by the Golang's design? If it 
>> > is allowed, I think there would be at least two Golang runtime running in 
>> > the same process space, am I correct?
>>
>> Assuming you are running on an ELF system and control symbol
>> visibility, this can work. As you say, you would have two different
>> Go runtimes in the same process, competing for access to the CPU and
>> virtual memory. To be clear, this is not supported by the Go project.
>>
>> Ian
>
> --
> You received this message because you are subscribed to the Google Groups 
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/golang-nuts/d787ab62-b1b7-4dd1-a2c9-cf8d3d7a4cb4n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcUC4B5JD2TYYAreZhUG_kMVGwgzidq0vgcBaCgCte18Cw%40mail.gmail.com.

Reply via email to