-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A question about vector #424
Comments
There are also some problems, such as the fact that the insert function in std supports different input parameters, while the stdgpu has only one parameter. There are also such problems in other places, are these specially made because of the features of the device side? |
While inserting at the the end of the container is straightforward, inserting from an arbitrary position would involve temporary memory allocations. Once could of course first shift the entries located after the insertion position to their new positions, but doing this in parallel only works reliably if the respective memory regions do not overlap (when Supporting more versions of So, these (documented) limitations are present since implementing these features on the device side efficiently is not trivial. Nevertheless, the situation is far from ideal and any suggestions for improvements are very welcome. |
I see. Thanks for the answer! |
The insert function here can only be inserted from the last position, which is obviously different from the intention of insert, which should be inserted from any position.
The text was updated successfully, but these errors were encountered: