Error print stack support use sub component field!

[taoistwar]

Feature Description

I use cursor gen a coponent, It alwasy crush. The error info does not has the knowledge.

scene:

slint

ScrollView {
      height = items-container.height
       items-container := VerticalLayout {
// snippets

       }
}

real error:

code height = items-container.height, use sub component field raise an error
Can this situation be detected and accurately reported?

report error:

thread '' panicked at D:\a\slint\slint\internal\core\properties.rs:539:9:
Recursion detected
stack backtrace:
0: 0x7ff85caaf26d - PyInit_slint
1: 0x7ff85c44a14b - slint_qt_get_widget
2: 0x7ff85caad584 - PyInit_slint
3: 0x7ff85caaf074 - PyInit_slint
4: 0x7ff85caad196 - PyInit_slint
5: 0x7ff85cabf913 - PyInit_slint
6: 0x7ff85cabf89f - PyInit_slint
7: 0x7ff85cac052e - PyInit_slint
8: 0x7ff85d197c31 - PyInit_slint
9: 0x7ff85c999529 - slint_new_path_events
10: 0x7ff85c9f4213 - slint_new_path_events
11: 0x7ff85c9fc5fa - slint_new_path_events
12: 0x7ff85c9c541b - slint_new_path_events
13: 0x7ff85ca22db5 - slint_new_path_events
14: 0x7ff85c996d2a - slint_new_path_events
15: 0x7ff85c9992a6 - slint_new_path_events
16: 0x7ff85c9f4273 - slint_new_path_events
17: 0x7ff85c9c7191 - slint_new_path_events
18: 0x7ff85c9c541b - slint_new_path_events
19: 0x7ff85ca22db5 - slint_new_path_events
20: 0x7ff85c9948ca - slint_new_path_events
21: 0x7ff85c7bf5c5 - send_keyboard_string_sequence
22: 0x7ff85c7d4bd9 - send_keyboard_string_sequence
23: 0x7ff85c7c3813 - send_keyboard_string_sequence
24: 0x7ff85c7d861d - send_keyboard_string_sequence
25: 0x7ff85c590885 - slint_qt_get_widget
26: 0x7ff85c531d3e - slint_qt_get_widget
27: 0x7ff85cbaa434 - PyInit_slint
28: 0x7ff85cba9b62 - PyInit_slint
29: 0x7ff85cba7904 - PyInit_slint
30: 0x7ff85cbb5425 - PyInit_slint
31: 0x7ff975067846 - CallWindowProcW
32: 0x7ff97506730c - CallWindowProcW
33: 0x7ff85c416c29 -
34: 0x7ff975067846 - CallWindowProcW
35: 0x7ff97506539d - IsWindowUnicode
36: 0x7ff85c514be5 - slint_qt_get_widget
37: 0x7ff85c5122da - slint_qt_get_widget
38: 0x7ff85c3fb07f -
39: 0x7ff886241519 - cfunction_vectorcall_NOARGS
at \Objects\methodobject.c:481
40: 0x7ff8861f3ce1 - _PyObject_VectorcallTstate
at \Include\internal\pycore_call.h:92
41: 0x7ff8861f4659 - PyObject_Vectorcall
at \Objects\call.c:325
42: 0x7ff88631af61 - _PyEval_EvalFrameDefault
at \PCbuild\Python\bytecodes.c:2715
43: 0x7ff886314616 - _PyEval_EvalFrame
at \Include\internal\pycore_ceval.h:89
44: 0x7ff886314616 - _PyEval_Vector
at \Python\ceval.c:1685
45: 0x7ff886314616 - PyEval_EvalCode
at \Python\ceval.c:580
46: 0x7ff88630fb36 - builtin_exec_impl
at \Python\bltinmodule.c:1093
47: 0x7ff88630d30f - builtin_exec
at \Python\clinic\bltinmodule.c.h:543
48: 0x7ff886241321 - cfunction_vectorcall_FASTCALL_KEYWORDS
at \Objects\methodobject.c:438
49: 0x7ff8861f3ce1 - _PyObject_VectorcallTstate
at \Include\internal\pycore_call.h:92
50: 0x7ff8861f4659 - PyObject_Vectorcall
at \Objects\call.c:325
51: 0x7ff88631af61 - _PyEval_EvalFrameDefault
at \PCbuild\Python\bytecodes.c:2715
52: 0x7ff886314616 - _PyEval_EvalFrame
at \Include\internal\pycore_ceval.h:89
53: 0x7ff886314616 - _PyEval_Vector
at \Python\ceval.c:1685
54: 0x7ff886314616 - PyEval_EvalCode
at \Python\ceval.c:580
55: 0x7ff88630fb36 - builtin_exec_impl
at \Python\bltinmodule.c:1093
56: 0x7ff88630d30f - builtin_exec
at \Python\clinic\bltinmodule.c.h:543
57: 0x7ff886241321 - cfunction_vectorcall_FASTCALL_KEYWORDS
at \Objects\methodobject.c:438
58: 0x7ff8861f3ce1 - _PyObject_VectorcallTstate
at \Include\internal\pycore_call.h:92
59: 0x7ff8861f4659 - PyObject_Vectorcall
at \Objects\call.c:325
60: 0x7ff88631af61 - _PyEval_EvalFrameDefault
at \PCbuild\Python\bytecodes.c:2715
61: 0x7ff8861f4934 - _PyFunction_Vectorcall
at \Objects\call.c:424
62: 0x7ff8861f45a6 - _PyVectorcall_Call
at \Objects\call.c:271
63: 0x7ff8861f46f6 - _PyObject_Call
at \Objects\call.c:354
64: 0x7ff88616e999 - PyObject_Call
at \Objects\call.c:379
65: 0x7ff88616e999 - pymain_run_module
at \Modules\main.c:300
66: 0x7ff88616f973 - pymain_run_python
at \Modules\main.c:631
67: 0x7ff88616ff08 - Py_RunMain
at \Modules\main.c:714
68: 0x7ff779ea1490 - invoke_main
at D:\a_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:90
69: 0x7ff779ea1490 - __scrt_common_main_seh
at D:\a_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
70: 0x7ff9745ce8d7 - BaseThreadInitThunk
71: 0x7ff9752ec53c - RtlUserThreadStart

Product Impact

No response

[ogoffart]

It would be nice to have an actual reproducible example.

I've tried this:

import { ScrollView } from "std-widgets.slint";

export component Demo {
    ScrollView {
        height: items-container.height;
        items-container := VerticalLayout {
            // snippets
       }
    }
}

And this gives actual error at compile time:

The binding for the property 'height' is part of a binding loop (flickable.height -> flickable.viewport-height -> flickable-viewport.height -> items-container.height -> height)

If it doesn't, this is a bug of the compiler that it doesn't see the loop for some reason.