Thanks jake.. If previous comments I received indicate that I should put the original question to rest,... but memguard.go suggests it should be re-opened
On Saturday, May 4, 2019 at 1:23:40 PM UTC-4, jake...@gmail.com wrote: > > On Friday, May 3, 2019 at 9:44:05 PM UTC-4, lgo...@gmail.com wrote: >> >> I'm currently working on a specialized encryption system where the keys >> are global... >> More importantly, I've been unable to locate any decent on-line docs >> describing exactly how Go GC works from a functional programming >> perspective..I found some docs describing various GC concepts and others >> that indicate how difficult a problem GC is, but nothing that tells me how >> Go's GC system works from a programmers perspective i.e. what happens when >> a function ends ? when main() ends ? >> >> >> I recall other discussions in this group about secure memory. At least > one person suggested https://github.com/awnumar/memguard. Probably worth > looking at, and doing more searching before reinventing the wheel. > > >> >> On Friday, May 3, 2019 at 8:50:00 PM UTC-4, Matt Harden wrote: >>> >>> On Fri, May 3, 2019, 17:28 <lgo...@gmail.com> wrote: >>> >>>> Does Go GC destroy all global vars prior to the end of main() ? >>>> >>> >>> What do you mean by "destroy"? Go is not an object oriented language and >>> doesn't have the concept of a destructor. So no, it doesn't, but it also >>> doesn't need to. >>> >>> May I ask, what led you to ask this question? >>> >> -- 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. For more options, visit https://groups.google.com/d/optout.
