You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The *.cpp files generated from *.slint files are not deterministic. Some struct member initialization code seems to have a random order (maybe coming from an unordered dict?). The problem is that this breaks ccache from being useful, thus wasting time during development.
Another case are embedded resources in the generated *.h files, which seem to be random too:
This is actually much worse as the generated header file will be included in many *.cpp files, causing ccache to fail on all those files too. In LibrePCB this currently leads to ~60 seconds of wasted time on every unnecessary rebuild.
I suspect this problem should be easy to fix, but would save a lot of time (and nerves).
Note that I can't say if there are more cases than the two mentioned, but I'd be happy to try again and report once these two are fixed.
Reproducible Code (if applicable)
Environment Details
Slint Version: Current master
Platform/OS: Linux
Programming Language: C++
Backend/Renderer:
Product Impact
No response
The text was updated successfully, but these errors were encountered:
Bug Description
The *.cpp files generated from *.slint files are not deterministic. Some struct member initialization code seems to have a random order (maybe coming from an unordered dict?). The problem is that this breaks ccache from being useful, thus wasting time during development.
Example of generated code:
Lines 17 and 25 contain random content:
Another case are embedded resources in the generated *.h files, which seem to be random too:
This is actually much worse as the generated header file will be included in many *.cpp files, causing ccache to fail on all those files too. In LibrePCB this currently leads to ~60 seconds of wasted time on every unnecessary rebuild.
I suspect this problem should be easy to fix, but would save a lot of time (and nerves).
Note that I can't say if there are more cases than the two mentioned, but I'd be happy to try again and report once these two are fixed.
Reproducible Code (if applicable)
Environment Details
master
Product Impact
No response
The text was updated successfully, but these errors were encountered: