Bump solang-parser from 0.2.4 to 0.3.3

[dependabot]

Bumps solang-parser from 0.2.4 to 0.3.3.

Release notes

Sourced from solang-parser's releases.

v0.3.3: Atlantis

This release improves the Solana developer experience, since now required accounts can be specified using annotations. For Polkadot, compatibility with Ethereum Solidity has been increased further, it is now possible to write EIP-1967 compatible proxy contracts. There are many fixes all over the code base.

Added

• Solana the required accounts for instructions can now be specified using function annotations. LucasSte

  contract Foo {
      @account(oneAccount)
      @signer(mySigner)
      @mutableAccount(otherAccount)
      @mutableSigner(otherSigner)
      function bar() external returns (uint64) {}
  }
  

• The language server can now format Solidity source code using the forge-fmt crate. chioni16
• The langauge server can now do go references, go to implementation, and go to type definition. chioni16
• Polkadot Panic errors can now be caught in try-catch statements xermicus
• Polkadot custom errors are now supported xermicus
• Polkadot now supporting the address.code builtin xermicus

Fixed

• Solana the data field of AccountInfo can now be modified. LucasSte
• The vscode extension now uses the solang binary in the path, if available. seanyoung
• Fixed a bug in the ABI encoding of dynamic arrays. xermicus
• Fixed a bug where loading from a storage struct member was not considered a storage read. xermicus seanyoung
• Fixed a compiler crash caused by chained assignments like return a = b. xermicus
• Variables declared in the return parameters no longer ignore the storage location. xermicus

Changed

• BREAKING: Solana the contract Solidity type can no longer be used. This type used to represent a single address, but this does not make sense asthere are many accounts associated with a contract call. LucasSte

v0.3.2

... (truncated)

Changelog

Sourced from solang-parser's changelog.

v0.3.3 Atlantis

This release improves the Solana developer experience, since now required accounts can be specified using annotations. For Polkadot, compatibility with Ethereum Solidity has been increased further, it is now possible to write EIP-1967 compatible proxy contracts. There are many fixes all over the code base.

Added

• Solana the required accounts for instructions can now be specified using function annotations. LucasSte

  contract Foo {
      @account(oneAccount)
      @signer(mySigner)
      @mutableAccount(otherAccount)
      @mutableSigner(otherSigner)
      function bar() external returns (uint64) {}
  }
  

• The language server can now format Solidity source code using the forge-fmt crate. chioni16
• The langauge server can now do go references, go to implementation, and go to type definition. chioni16
• Polkadot Panic errors can now be caught in try-catch statements xermicus
• Polkadot custom errors are now supported xermicus
• Polkadot now supporting the address.code builtin xermicus

Fixed

• Solana the data field of AccountInfo can now be modified. LucasSte
• The vscode extension now uses the solang binary in the path, if available. seanyoung
• Fixed a bug in the ABI encoding of dynamic arrays. xermicus
• Fixed a bug where loading from a storage struct member was not considered a storage read. xermicus seanyoung
• Fixed a compiler crash caused by chained assignments like return a = b. xermicus
• Variables declared in the return parameters no longer ignore the storage location. xermicus

Changed

• BREAKING: Solana the contract Solidity type can no longer be used. This type used to represent a single address, but this does not make sense as there are many accounts associated with a contract call. LucasSte

v0.3.2 Brasília

The language server is much improved, and many fixes all over.

Added

• Go to definition is now implemented in the language server. chioni16
• The parser has been updated to be compatible with Ethereum Solidity v0.8.21. seanyoung
• Polkadot Support for runtimes built with on polkadot-v1.0.0

Fixed

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)