You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lazy segment tree of this is repo very useful when exactly the operations that it has are needed, but when other are needed it is difficult to modify because it is not very clear where the lazy values are propagated and where the operations are made.
In normal segment tree on the other hand is very easy to modify the operation because it is in a separate function.
I propose making a similar separation for lazy segment tree.
Probably it wold look something like this: https://github.com/IvanRenison/icpc-team-notebook-el-vasito/blob/update_STree_lazy/data_structures/segment_tree_lazy.cpp (note that that lazy segment tree is different because it is not lazy in memory allocation)
If you are interested in this improvement I can make it (including the tests) and send a pull request.
The text was updated successfully, but these errors were encountered:
IvanRenison
changed the title
Lazy segment tree is dificult to modiafy for other operations
Lazy segment tree is difficult to modify for other operations
Jul 14, 2023
The lazy segment tree of this is repo very useful when exactly the operations that it has are needed, but when other are needed it is difficult to modify because it is not very clear where the lazy values are propagated and where the operations are made.
In normal segment tree on the other hand is very easy to modify the operation because it is in a separate function.
I propose making a similar separation for lazy segment tree.
Probably it wold look something like this: https://github.com/IvanRenison/icpc-team-notebook-el-vasito/blob/update_STree_lazy/data_structures/segment_tree_lazy.cpp (note that that lazy segment tree is different because it is not lazy in memory allocation)
If you are interested in this improvement I can make it (including the tests) and send a pull request.
The text was updated successfully, but these errors were encountered: