Considering that we use toArray() at another location, it might be good to investigate (or just remove the method entirely).
Adding this to the 1.6 Milestone, since it can probably be closed once there is no more ConstHybridVector. If we still use some form of ConstHybridVector, it would be good to double-check this issue.
See the discussion in #1. The commit https://github.com/slizzered/haseongpu/commit/459d61af023913ef9b14d8771bab77cf240c6b91 was sufficient to fix it, which seems weird to me.
Considering that we use
toArray()at another location, it might be good to investigate (or just remove the method entirely).Adding this to the 1.6 Milestone, since it can probably be closed once there is no more ConstHybridVector. If we still use some form of ConstHybridVector, it would be good to double-check this issue.