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

EIP-29 attachment implementation #154

Merged
merged 19 commits into from
Apr 25, 2022
Merged

EIP-29 attachment implementation #154

merged 19 commits into from
Apr 25, 2022

Conversation

MrStahlfelge
Copy link
Member

@MrStahlfelge MrStahlfelge commented Mar 29, 2022

Adds implementation for current version of ergoplatform/eips#58

@MrStahlfelge MrStahlfelge marked this pull request as ready for review March 29, 2022 15:00
@MrStahlfelge
Copy link
Member Author

Added a unit test demonstrating the type declaration problem, please take a look.

@MrStahlfelge
Copy link
Member Author

The test is fixed but intErgoValue.getValue() still returns an Integer but declares to return scala.Int - so the declaration is still not correct and the test fix works because it is going through a Scala layer.

The test itself is not the problem, it was just my demonstration. We've got to make the following decision: should the ErgoValue<> contain Scala types or not?

  • If yes, it must be changed to return Scala types, probably by using a Scala layer. Problem: Will break existing code using Java types
  • If no, return values must be changed. Problem: Could introduce bugs for recursive ErgoTrees

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.

2 participants