Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.3.0 Venice #1319

Merged
merged 1 commit into from
May 22, 2023
Merged

v0.3.0 Venice #1319

merged 1 commit into from
May 22, 2023

Conversation

seanyoung
Copy link
Contributor

@seanyoung seanyoung commented May 19, 2023

The parser and semantic analysis stage of Solang have gone through
a security audit. All security issues have been fixed.

Added

  • The CLI now has a --release option, which disables printing of errors salaheldinsoliman
  • Substrate: chain extensions can be now used.
    xermicus

Fixed

  • Solidity error definitions are now parsed.
    seanyoung
  • The Ethereum Solidity parser and semantic analysis tests are now run on Solang sema during
    cargo test.
    seanyoung
  • If a function returns a storage reference, then not returning a value explicitly is an error, since
    the reference must refer to an existing storage variable.
    seanyoung
  • Many small improvements have been made to the parser and semantic analysis, improving compatibility
    with Ethereum Solidity.
    seanyoung
    xermicus
    LucasSte

Changed

  • Solana: Addresses are now base58 encoded when formated with "address:{}".format(address).
    LucasSte
  • Substrate: No longer use the prefixed names for seal runtime API calls, which grants small improvements in contract sizes. xermicus

Copy link
Contributor

@xermicus xermicus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I've added some more of my contributions

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Outdated
@@ -2,6 +2,36 @@
All notable changes to [Solang](https://github.com/hyperledger/solang/)
will be documented here.

## v0.3.0 Venice

The parser and semantic analysis stage of Solang have been through
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think have gone through or underwent sounds better than have been through.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed to have gone through but I have a hard time seeing any difference - other than taste.

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated
`cargo test`.
[seanyoung](https://github.com/seanyoung)
- If a function returned a `storage` reference, then not returning a value explicitly is an error, since
the reference must post refer to an existing variable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Post refer?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that was a brain misfire, I am sure I was thinking about the variables post function execution. Anyway fixed

[seanyoung](https://github.com/seanyoung)
[xermicus](https://github.com/xermicus)
[LucasSte](https://github.com/LucasSte)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is is worth mentioning the changes in the stdlib?
Tests are now enabled and we build the files when running cargo build. These changes do not affect the users in any way, so they are not really worth a place in the change log.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say the changelog should only document user-facing changes.

CHANGELOG.md Outdated Show resolved Hide resolved
The parser and semantic analysis stage of Solang have gone through
[a security audit](https://github.com/solana-labs/security-audits/blob/master/solang/Trail_of_Bits_Solang_Final_report.pdf). All security issues have been fixed.

### Added
- The CLI now has a `--release` option, which disables printing of errors [salaheldinsoliman](https://github.com/salaheldinsoliman)
- **Substrate**: chain extensions can be now used.
  [xermicus](https://github.com/xermicus)

### Fixed
- Solidity error definitions are now parsed.
  [seanyoung](https://github.com/seanyoung)
- The Ethereum Solidity parser and semantic analysis tests are now run on Solang sema during
  `cargo test`.
  [seanyoung](https://github.com/seanyoung)
- If a function returns a `storage` reference, then not returning a value explicitly is an error, since
  the reference must refer to an existing storage variable.
  [seanyoung](https://github.com/seanyoung)
- Many small improvements have been made to the parser and semantic analysis, improving compatibility
  with Ethereum Solidity.
  [seanyoung](https://github.com/seanyoung)
  [xermicus](https://github.com/xermicus)
  [LucasSte](https://github.com/LucasSte)

### Changed
- **Solana**: Addresses are now base58 encoded when formated with `"address:{}".format(address)`.
  [LucasSte](https://github.com/LucasSte)
- **Substrate**: No longer use the prefixed names for seal runtime API calls, which grants small improvements in contract sizes. [xermicus](https://github.com/xermicus)

Signed-off-by: Sean Young <[email protected]>
@seanyoung seanyoung merged commit 53172f3 into hyperledger:main May 22, 2023
@seanyoung seanyoung deleted the release branch May 22, 2023 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants