Skip to content

Wizard: Optimize test project compilation #1303

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
immrsd opened this issue Jan 14, 2025 · 0 comments
Closed

Wizard: Optimize test project compilation #1303

immrsd opened this issue Jan 14, 2025 · 0 comments
Assignees
@immrsd
Milestone
1. current

Comments

@immrsd
Copy link
Collaborator

immrsd commented Jan 14, 2025

Compilation of a generated test project takes too much time and RAM which makes it almost infeasible to compile. We should come up with a solution for that. One possible solution is to split test project into separate projects (or packages?) per contract kind.
@immrsd immrsd moved this to 📋 Backlog in Contracts for Cairo Jan 14, 2025
@immrsd immrsd added this to the 1. current milestone Jan 14, 2025
@ericnordelo ericnordelo moved this from 📋 Backlog to 🏗 In progress in Contracts for Cairo Mar 25, 2025
@immrsd immrsd moved this from 🏗 In progress to 👀 In review in Contracts for Cairo Mar 25, 2025
@immrsd immrsd moved this from 👀 In review to ✅ Resolved in Contracts for Cairo Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@immrsd immrsd

Labels
None yet
Projects
Contracts for Cairo
Archived in project
Milestone
1. current
Development

No branches or pull requests
2 participants
@ericnordelo @immrsd