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

Add Lazy and use it throughout Plutus Tx code instead of the slower () #6060

Closed
effectfully opened this issue May 20, 2024 · 2 comments
Closed

Comments

@effectfully
Copy link
Contributor

effectfully commented May 20, 2024

We should have some kind of Lazy data type instead of using () -> in Plutus Tx, so that we can compile it to delay and force instead of juggling the slower units.

This applied to builtins too, i.e. ifThenElse, chooseList, chooseData and whatever else builtins we have shouldn't be instantiated with () ->, it should be Lazy in there.

@github-actions github-actions bot added the status: needs triage GH issues that requires triage label May 20, 2024
@effectfully effectfully removed the status: needs triage GH issues that requires triage label May 20, 2024
@bezirg
Copy link
Contributor

bezirg commented May 20, 2024

I had some PR somewhere that was going through a uplc program and turned all unused variables (no occurences in the body) and was turning them to delay and force. I don't know where is that PR now. But your approach sounds better.

@effectfully
Copy link
Contributor Author

Closing in favor of #5967.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants