Sophie Dankel
Sophie Dankel
This log message occurs often and should really be DEBUG or INFO rather than WARN level.
Currently there is no hover information shown for storage fields. With the [documentation](https://github.com/FuelLabs/sway-standards/issues/5) guidelines saying to write comments on storage fields rather than at the top of the storage declaration,...
We should show the constant's type in the hover docs like we do for variables. Currently we show the doc comments but nothing else.  
In rust these take you to the appropriate page in docs.rs. Since we don't have docs for every sway crate hosted, for now we could make these into go-to links....
## Description Related https://github.com/FuelLabs/sway-vscode-plugin/pull/166 Adds a [DAP](https://microsoft.github.io/debug-adapter-protocol//) server as a new forc plugin, `forc-debug`. This enables a UI debugging experience in IDEs such as VSCode. For now, only debugging forc...
@SilentCicero suggested a library in sway similar to rust's [dbg](https://doc.rust-lang.org/std/macro.dbg.html) that prints debug information.
We should add a command like `forc debug serve` that starts a [DAP](https://microsoft.github.io/debug-adapter-protocol/specification) server for the LSP to communicate with. The server will be essentially a passthrough to the fuel...
@kayagokalp and I did an analysis of what's missing spans after the IR stage with optimization disabled. We found that almost everything is there, except for the return value spans....
`forc init` generates a default forc project. Currently the files it generates look like this: `Forc.toml` ```toml [project] authors = ["Sophie"] entry = "main.sw" license = "Apache-2.0" name = "some_name"...
for this test: ```sway contract; struct MyStruct { a: u64, b: Option } impl Eq for MyStruct { fn eq(self, other: Self) -> bool { __eq(self.a, other.a) } } #[test]...