[new compiler] Improved error handling

* When reporting errors with literal bindings, use the correct location for the report,
  the place where the literal value is declared.
* Create property caches for group properties, so that later in the property
  validator we can do extra checks
* Report an error when trying to declare an object to the default property of a group
  property
* Similarlyl report an error when trying to use sub-objects with value type properties
* Temporarily change tst_qqmllanguage::errors() to also try to instantiate the component,
  because for the moment some errors are only reported at instantiating time instead of
  compile time. That'll be fixed later when move checks get moved into the property validator.

Change-Id: Icaa8d2edc7918c03001c40fba7880ee5cac10e69
Reviewed-by: Lars Knoll <lars.knoll@digia.com>

1 files changed, 4 insertions, 2 deletions

diff --git a/tests/auto/qml/qqmllanguage/tst_qqmllanguage.cpp b/tests/auto/qml/qqmllanguage/tst_qqmllanguage.cpp
index 6110e4870f..fade1256b0 100644
--- a/tests/auto/qml/qqmllanguage/tst_qqmllanguage.cpp
+++ b/tests/auto/qml/qqmllanguage/tst_qqmllanguage.cpp
@@ -520,11 +520,13 @@ void tst_qqmllanguage::errors()
 {
     QFETCH(QString, file);
     QFETCH(QString, errorFile);
-    QFETCH(bool, create);
+    // ### FIXME: re-enable these create "checks" when the new compiler is default and does property binding compatibility tests
+    // in the loader thread.
+//    QFETCH(bool, create);
 
     QQmlComponent component(&engine, testFileUrl(file));
 
-    if(create) {
+    if (/*create && */component.isReady()) {
         QObject *object = component.create();
         QVERIFY(object == 0);
     }