Open kunaltyagi opened 4 years ago
Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.
Hi, can I work on this issue? I can see a merged and an open branch referring to this issue right now, so if this performance improvement is still desirable I'd like to help with this.
Hi, can I work on this issue? I can see a merged and an open branch referring to this issue right now, so if this performance improvement is still desirable I'd like to help with this.
Great that you want to work on this, however I am not sure how to proceed here. I think we first have to review the open (draft) pull request above, and see whether we have to make any design decisions. Until then, maybe you find another open issue that interests you?
Is your feature request related to a problem? Please describe.
Some older implementations of filters (at least PassThrough and ConditionalRemoval) are very slow compared to what can be achieved by FunctorFilter (introduced by #3890)
Context
Source Code
```cpp #includeExpected behavior
PCL should not offer duplicate features, specially when the one that is easier to use, search and stumble upon also provides much worse performance. In this case,
std::function
😄PassThrough
😱ConditionalRemoval
🙀Describe the solution you'd like
For simple filters (such as PassThrough and ConditionalRemoval, etc.), we should either
This allows downstream users to get performance improvements (or notifications about a faster way) and also prevents new users from misusing the library. Depending on the decision, we would need to modify the docs and highlight the new feature