[Bf-blender-cvs] [ddeaa42a356] virtual-array-attributes: Geometry Nodes: Use virtual arrays in internal attribute api (WIP).

[Jacques Lucke]

Commit: ddeaa42a35621a4f8877ffc3c81a03122232d895
Author: Jacques Lucke
Date:   Fri Apr 16 15:44:46 2021 +0200
Branches: virtual-array-attributes
https://developer.blender.org/rBddeaa42a35621a4f8877ffc3c81a03122232d895

Geometry Nodes: Use virtual arrays in internal attribute api (WIP).

Differential Revision: https://developer.blender.org/D10994

===================================================================

M	source/blender/blenlib/BLI_virtual_array.hh

===================================================================

diff --git a/source/blender/blenlib/BLI_virtual_array.hh b/source/blender/blenlib/BLI_virtual_array.hh
index 615e1dd9b35..fced85bc090 100644
--- a/source/blender/blenlib/BLI_virtual_array.hh
+++ b/source/blender/blenlib/BLI_virtual_array.hh
@@ -30,7 +30,7 @@
  * specific format required for the function. This can be a costly conversion if only few of the
  * elements are accessed in the end.
  *
- * Functions taking a virtual array as input can still optimize for different data layouts. _For_
+ * Functions taking a virtual array as input can still optimize for different data layouts. For
  * example, they can check if the array is stored as an array internally or if it is the same
  * element for all indices. Whether it is worth to optimize for different data layouts in a
  * function has to be decided on a case by case basis. One should always do some benchmarking to