graphics: Revive the special allocating method for vertices for Wasm

It looks like the allocation cost is pretty high even on Wasm. Revive the special method not only on GopherJS but also on Wasm. examples/sprites kept 30FPS without this fix, but keeps 35FPS with this fix, on Hajime's MacBook Pro 2020 (macOS Catalina 10.15.6). Updates hajimehoshi#797
momodezhou · Sep 20, 2020 · cb73230 · cb73230
1 parent 8d17ec8
commit cb73230
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/internal/graphics/vertex.go b/internal/graphics/vertex.go
@@ -83,8 +83,8 @@ func (v *verticesBackend) slice(n int, last bool) []float32 {
 }
 
 func vertexSlice(n int, last bool) []float32 {
-	if web.IsGopherJS() {
-		// In GopherJS, allocating memory by make is expensive. Use the backend instead.
+	if web.IsBrowser() {
+		// In GopherJS and Wasm, allocating memory by make is expensive. Use the backend instead.
 		return theVerticesBackend.slice(n, last)
 	}
 	return make([]float32, n*VertexFloatNum)