Brief synopsis: Go 1.8 is moving to a hybrid write barrier in order to eliminate stack rescanning. The hybrid write barrier is equivalent to the "double write

Brief synopsis: Go 1.8 is moving to a hybrid write barrier in order to eliminate stack rescanning. The hybrid write barrier is equivalent to the "double write barrier" used in the adaptation of Metronome used in the IBM real-time Java implementation. Some benchmarks: https://github.com/golang/go/commit/bd640c882a8dcb88a0497770f881bce48ab83102 https://github.com/golang/go/commit/bd640c882a8dcb88a0497770...