On Mon, Jul 11, 2016 at 1:25 PM, <sphilip...@gmail.com> wrote: > Ohh that slooooow gcc. Sad.
The GC in general is quite fast. If you have specific examples where the GC does poorly, please open issues for them with test cases. Thanks. Ian > понедельник, 11 июля 2016 г., 23:03:07 UTC+3 пользователь Ian Lance Taylor > написал: >> >> On Mon, Jul 11, 2016 at 9:11 AM, <sphil...@gmail.com> wrote: >> > Thank for answer but I'm already implemented portable unmanaged memory >> > pool >> > (https://github.com/ardente/goal/blob/master/gut/mempool.go). I'm just >> > looking for standard direct analogue (incliding mapping of fd -1) of >> > unix's >> > syscall.Mmap for windows. Looks like there is none. There is some >> > rationale >> > behind this or just lack of time/interest? >> >> This is not something most Go programs are expected to do. >> >> Most Go programs that need to allocate memory that is not controlled >> by the Go garbage collector are programs that already use cgo. Those >> programs can use C.malloc, which works on all systems. >> >> 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. > For more options, visit https://groups.google.com/d/optout. -- 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.
