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 --target into subcommands for dev tree compile and other improvements #2713

Merged
merged 16 commits into from
Apr 16, 2024

Conversation

janmasrovira
Copy link
Collaborator

@janmasrovira janmasrovira commented Apr 9, 2024

  • refactor --target into subcommands for dev tree compile.
  • prepend App to all CompileTarget constructors to avoid name clashes with Target.
  • parameterize compile options type with the input kind. The input kind indicates the expected file extension of the input file. If the input file is a .juvix file, then it is optional, otherwise it is mandatory.
  • Add AppError MegaparsecError instance and simplify some related code.

@janmasrovira janmasrovira added enhancement New feature or request refactor labels Apr 9, 2024
@janmasrovira janmasrovira self-assigned this Apr 9, 2024
@janmasrovira janmasrovira changed the title refactor --target in to subcommands for dev xxx compile refactor --target into subcommands for dev xxx compile Apr 9, 2024
@janmasrovira janmasrovira force-pushed the dev-subcommands branch 2 times, most recently from 8cf9892 to afb002e Compare April 15, 2024 13:50
@janmasrovira janmasrovira changed the title refactor --target into subcommands for dev xxx compile refactor --target into subcommands for dev tree compile Apr 16, 2024
@janmasrovira janmasrovira changed the title refactor --target into subcommands for dev tree compile refactor --target into subcommands for dev tree compile and other improvements Apr 16, 2024
@janmasrovira janmasrovira marked this pull request as ready for review April 16, 2024 08:05

instance EntryPointOptions (CasmOptions k) where
applyOptions opts =
set entryPointTarget (Just TargetCairo) -- TODO is this the right target?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's the right target, because CASM can only be compiled to Cairo, so it's useless to make a separate backend target for it (whose purpose is to establish implementation limits like max number of function arguments, etc).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done 98ac944

Copy link
Collaborator

@lukaszcz lukaszcz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove TODO comment and resolve conflicts preserving the changes from #2728

@lukaszcz lukaszcz merged commit 65176a3 into main Apr 16, 2024
4 checks passed
@lukaszcz lukaszcz deleted the dev-subcommands branch April 16, 2024 15:32
paulcadman added a commit that referenced this pull request Apr 18, 2024
The wasm32-wasi target was renamed to wasi in #2713
janmasrovira pushed a commit that referenced this pull request Apr 19, 2024
The wasm32-wasi target was renamed to wasi in #2713
paulcadman added a commit that referenced this pull request Apr 22, 2024
The wasm32-wasi target was renamed to wasi in #2713
janmasrovira pushed a commit that referenced this pull request Apr 23, 2024
The wasm32-wasi target was renamed to wasi in #2713
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants