Igor Rončević

General remark. @tritao's concern about debug symbols and loosing span information when desugaring is valid, especially in this approach when we generate the code by compiling code snippets. It looks...

When I compile this simple predicate: ```Sway predicate; fn main() -> bool { true } ``` the compiler panics in `aut_impl`: ``` thread 'main' panicked at sway-core/src/semantic_analysis/ast_node/declaration/auto_impl.rs:679:9: Handler { inner:...

> This is also a choice we need to make. When I generate code that calls things that live inside core I opted to not put the complete path so...

> How were you pointing to the new compiler and the new core? I've just created a new predicate with `forc new --predicate` and then run: ``` repos/sway$ cargo run...

Blocked by #5562 (only the first two tasks are needed to properly solve this issue). If urgent, we can provide a workaround and fix this issue before getting the first...

Closed in #5643.

Hi @postmeback, thanks for your willingness to contribute! This issue actually depends on the outcome of #21 and it might be that it will be obsolete after #21 is closed....

> I believe that #4878 closes this issue as well As explained in the [comment](https://github.com/FuelLabs/sway/pull/4878#issuecomment-1656188166), #4878 does not close this issues, but #21 could render it obsolete.

Yes there is a single module in the test suite harness checking exactly that (and few other points). I assume it shouldn't be too difficult to extract the check logic...

> This relies on all statements being either declarations or expressions, and in particular on control flow statements being expressions that return (). This is also how I see it....