16 Nov
2024
16 Nov
'24
11:07 a.m.
3. What's the rationale behind BOOST_SQLITE_NO_VIRTUAL? Wouldn't setting it cause trouble, being a compiled library?
It would. The idea is that you can use that for constrained (i.e. embedded environments) to avoid the unnecessary vtable and to enforce devirtualization if your compiler misses this.
If I have read the code correctly, these functions seem to only be used in headers. Why do they need to be virtual? It looks like it could have been made a compile-time interface (i.e. a concept), completely avoiding the need for the macro. What's the rationale behind this?