Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
QtCS2017 Before Runtime discussion: Difference between revisions
Jump to navigation
Jump to search
Tim.Jenssen (talk | contribs) (→Notes) |
Tim.Jenssen (talk | contribs) (→Notes) |
||
| Line 14: | Line 14: | ||
* the tools cannot fit to all cases | * the tools cannot fit to all cases | ||
* this kind of tools can help to move to Qt 6(or other future versions) | * this kind of tools can help to move to Qt 6(or other future versions) | ||
* renaming methods would be easier with this kind of tools | |||
== Make changes easy == | == Make changes easy == | ||
Revision as of 11:35, 9 October 2017
Make the API easy?
- Copy on Write to avoid copies at runtime
- Can we do it at compile time?
- Let tools get const and references right
- Warn about unnecessary copies
- Clang can help here
Notes
- need real examples
- QtCreator supports only very basic refactoring tools
- having tools outside of QtCreator and use these tools maybe inside
- API changes need to be available by Clangtidy scripts (?)
- what about templates?
- concept
- the tools cannot fit to all cases
- this kind of tools can help to move to Qt 6(or other future versions)
- renaming methods would be easier with this kind of tools
Make changes easy
- API changes are expensive
- API looks outdated if not adapted to current paradigms (legacy code)
- How can we make them easy
- How can Clang help here
Clang Query
- Think about it as SQL for the AST
- Makes big changes much cheaper and secure
Immediate feedback vs overnight refactoring
- Both are important
- Immediate feedback reduces refactorings and reviews
- Run refactorings overnight for expansive refactorings
- Integration with the CI