Denis Blank

Thanks for your report. The `uninitialized-member` warning is triggered because some members are initialized in the content of the constructor, mayne this can be improved. The other warnings will be...

Hey, thanks for your issue report. I thought about this and decided that it is more a feature request than an actual issue of the library, which I don't want...

The readme text could be misleading here: Usually the underlying erased object should be responsible for invalidating its state if called through a R-value qualified `operator() (...) &&`, but in...

This sounds like a promising feature. Probably I will implement it in the future.

Thank you for your report. I'm quite certain that this is a false positive. I will take a closer look into it.

Good suggestion, maybe this will be added in the future.

Yes, you are right, the assertion message is misleading indeed. Could you open a pull request with a message which would fit best in your opinion?

From my point of view this is the intended behaviour here because there is no way to access a method qualified as const from a non const context without ignoring...

Seems like there is a bug in the implementation, I'll provide a fix for that soon.

i can confirm this