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

Refactor wasm target and clarity-vm handling #1647

Open
Tracked by #1672
hugocaillard opened this issue Jan 23, 2025 · 0 comments
Open
Tracked by #1672

Refactor wasm target and clarity-vm handling #1647

hugocaillard opened this issue Jan 23, 2025 · 0 comments
Assignees

Comments

@hugocaillard
Copy link
Collaborator

  • Since Clarinet compiles to wasm, it use condtional compilation based in cargo features. Most of the work components expose a cli and wasm feature (clarity-repl/cli and clarity-repl/wasm), it leads to unnecessary complexity and should instead use conditional compilation based on the target
  • clarity-repl re-exports clarity-vm modules, I leads to some confusion and difficult dependency management. Other crates should rely on the clarity crates instead (and less on clarity-repl)
@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Jan 23, 2025
@hugocaillard hugocaillard moved this from 🆕 New to 📋 Backlog in DevTools Feb 6, 2025
@hugocaillard hugocaillard self-assigned this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant