Qt Contributors Summit 2019 - moc and QMetaObject
Jump to navigation
Jump to search
- breaking ABI allows for performance changes and additional features in QMetaObject
- what about newer C++ features
- raw literals are an issue e.g. like in tests
- worse, error handling is confusing and makes it hard for users to know what's going on
- can we use libclang instead of workarounds?
- libclang can be quite slow, but we already did it for lupdate and qdoc
- roughly an order of magnitude slower, but we could do better?
- when using build farms, moc is a bottleneck - unless it could be distributed but that doesn't sound feasible
- bootstrapping is quasi impossible when using libclang, we'd have to port moc to not use C++ anymore
- raw literals are an issue e.g. like in tests