IGI-111

Results 106 issues of IGI-111

Binary encoding of arbitrary sway values is a necessary feature, notably to return values/pass values to contracts in a predictable, portable fashion. This is tricky and solidity has had to...

compiler
lib: std
ABI
epic

In some cases, such as when loading code from a contract within an LDC proxy, it's possible to mix code that uses the same storage context. For instance, let's say...

enhancement
language feature
storage

`sway-ir`'s printer is not structured in a way that easily allows one to print a single instruction, which makes for cryptic error messages when problems are detected at the IR...

enhancement
good first issue
compiler: ir

Performance data is currently recorded using the normal github actions runner, which can produce unreliable results, we should make sure it runs on a similarly sized idle machine every single...

ci
compiler: performance-data

Now that we can visualize it, performance data has some odd patterns that might reflect bugs in how it's collected in or out of the compiler, namely that the bytecode...

bug
compiler: performance-data

Performance data recorded in https://github.com/FuelLabs/sway-performance-data can be found in multiple formats that don't contain the same information, we should consider standardizing it (and retroactively migrating the existing data). See [this...

code quality
compiler: performance-data

Refactor the way we build namespaces and type check into a separate step that resolves all the symbols to unique paths/ids before type checking. This should help us with issues...

big
code quality
compiler: frontend
compiler: collection