# 10.4 已知各类问题(Known Issues and Workarounds)

### 已知的问题(Known Issues)

* [#870](https://github.com/FuelLabs/sway/issues/870): All `impl` blocks need to be defined before any of the functions they define can be called. This includes sibling functions in the same `impl` declaration, i.e., functions in an `impl` can't call each other yet.\
  [#870](https://github.com/FuelLabs/sway/issues/870)：所有`impl`块都需要先定义，然后才能调用它们定义的任何函数。这包括同一`impl`声明中的同级函数，即`impl`中的函数还不能互相调用。

### 缺少的功能 (Missing Features)

* [#1182](https://github.com/FuelLabs/sway/issues/1182) Arrays in a `storage` block are not yet supported. See the [Manual Storage Management](https://fuellabs.github.io/sway/v0.38.0/book/blockchain-development/storage.html#manual-storage-management) section for details on how to use `store` and `get` from the standard library to manage storage slots directly. Note, however, that `StorageMap<K, V>` *does* support arbitrary types for `K` and `V` without any limitations.\
  [#1182](https://github.com/FuelLabs/sway/issues/1182) 尚不支持 `存储 storage`块中的数组。有关如何使用`store`的详细信息，请参阅[手动存储管理](https://fuellabs.github.io/sway/v0.38.0/book/blockchain-development/storage.html#manual-storage-management)部分并从标准库中`get`直接管理存储槽。但请注意，`StorageMap<K, V>`确实支持`K`和`V`的任意类型，没有任何限制。

### 常规问题 (General)

* No compiler optimization passes have been implemented yet, therefore bytecode will be more expensive and larger than it would be in production. Note that eventually the optimizer will support zero-cost abstractions, avoiding the need for developers to go down to inline assembly to produce optimal code.\
  尚未实现编译器优化过程，因此字节码将比生产中的字节码更昂贵且更大。请注意，优化器最终将支持零成本抽象，从而避免开发人员需要进行内联汇编来生成最佳代码。