Skip to content

Commit

Permalink
Merge pull request #108 from onflow/supun/interface-removal-docs
Browse files Browse the repository at this point in the history
Explain why conformance removal is not allowed
  • Loading branch information
SupunS authored May 30, 2024
2 parents 4de5cab + 6565223 commit 01d5580
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions docs/language/contract-updatability.md
Original file line number Diff line number Diff line change
Expand Up @@ -225,6 +225,9 @@ A field may belong to a contract, struct, resource, or interface.
pub struct Foo {
}
```
This is because if there was a container of type `T` (i.e: an array `[T]` or dictionary `{R:T}`, etc.),
and if a `Foo` value had been stored in that container, then that container value will become invalid,
as it will now hold a value that does not conform to `T`.

### Updating Members
Similar to contracts, these composite declarations: structs, resources, and interfaces also can have fields and
Expand Down

0 comments on commit 01d5580

Please sign in to comment.