Skip to content

processing of WASM opcodes #6820

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.

Sign up for GitHub

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

Jump to bottom
Closed
1010adigupta opened this issue Jan 16, 2024 · 2 comments
Closed

processing of WASM opcodes #6820

1010adigupta opened this issue Jan 16, 2024 · 2 comments
Labels
T-feature Type: feature

Comments

@1010adigupta
Copy link
Contributor

Component

Forge

Describe the feature you would like

I think Foundry is not able to recognise WASM opcodes now, due to which I am not able to get gas reports of Stylus contracts using foundry, even though they are fully interoperable with solidity contracts.
can anyone tell me if this feature is in the pipeline? if not then I would like to work on this.

Additional context

No response
@1010adigupta 1010adigupta added the T-feature Type: feature label Jan 16, 2024
@gakonst gakonst added this to Foundry Jan 16, 2024
@github-project-automation github-project-automation bot moved this to Todo in Foundry Jan 16, 2024
@mds1
Copy link
Collaborator

mds1 commented Jan 16, 2024

Just noting this is related to the broader issue of #748

@DaniPopes
Copy link
Member

WASM and Stylus are completely out of scope of this project.

@DaniPopes DaniPopes closed this as not planned Won't fix, can't repro, duplicate, stale Jan 19, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Foundry Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-feature Type: feature
Projects
Foundry
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mds1 @DaniPopes @1010adigupta