25b2645201
Type resolver can collect (presumably C++) type names which is needed to verify that the QML document we are about to compile is named correctly and does not have name conflicts However, the collection logic gathers everything we can find: C++ names, QML names, names marked with $anonymous$ or under import namespace. At the same time, the way the procedure works involves poking (pretty much) every known QQmlJSScope a.k.a. creates every type (previously some could've been deferred) which usually means that we have a larger than necessary footprint Thus, delete this procedure and simplify the code. We can later revisit the logic and figure the proper way to collect relevant type names. For now this is just overkill though. Note that this change, consequently, should avoid instantiating types imported from implicit import dir, instead of imported from qmldir (there is a difference apparently) Task-number: QTBUG-100103 Pick-to: 6.3 Change-Id: Iaf65e5f3a9bf53286760af0dc39a1d7036d7c474 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> |
||
|---|---|---|
| .. | ||
| qml | ||
| qmlcachegen | ||
| qmldom | ||
| qmleasing | ||
| qmlformat | ||
| qmlimportscanner | ||
| qmljs | ||
| qmljsrootgen | ||
| qmllint | ||
| qmlls | ||
| qmlplugindump | ||
| qmlpreview | ||
| qmlprofiler | ||
| qmlscene | ||
| qmltc | ||
| qmltestrunner | ||
| qmltime | ||
| shared | ||
| CMakeLists.txt | ||