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
As you can see, we start with the easiest file, which zig can do, then we up the complexity, which zig can't do, when going back down to the easier file with update, zig still is stuck on its past errors.
Failing test case:
Case 'importing builtin': unexpected errors at update_index=2:
========================================
:20:16: error: struct 'struct {}' has no member named 'output_mode'
========================================
The text was updated successfully, but these errors were encountered:
The test case is wrong because it should not be a compile error. After merging #8554 the expected behavior happens, which is to successfully compile all 3 times.
Did this issue ever even apply to master branch? The issue tracker is for master branch only.
As you can see, we start with the easiest file, which zig can do, then we up the complexity, which zig can't do, when going back down to the easier file with update, zig still is stuck on its past errors.
Failing test case:
The text was updated successfully, but these errors were encountered: