Compliance/current to new standard #60
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r vial build tool Co-authored-by: ojas_the_gr8 <[email protected]>
…ier in ArrayLiteralExpr
- Introduced a new build.hlx file to define build targets and configurations. - Created api.hlx to encapsulate the build API, including functions for setting targets, sources, includes, and build directories. - Implemented runtime.hlx to manage the execution of the build process and handle compiler configurations. - Enhanced vial.hlx to integrate the new build system, including functions for setting up the build environment, compiling sources, and linking artifacts. - Added error handling for missing compilers and runtime files. - Established a logging mechanism to track the build process and errors.
…or cross-platform support
…constraints also change generic syntax to the new standard
- Updated CX_Class, CX_Extend, CX_Function, CX_Interface, CX_Operator, CX_Struct to unify handling of function and operator declarations. - Changed references from OpDecl to FuncDecl where appropriate to streamline code and improve clarity. - Added checks for operator functions to ensure they are processed correctly, including validation for missing names. - Enhanced error handling for function declarations in interfaces and structs to enforce forward declaration rules. - Adjusted code generation logic to accommodate the new structure of function and operator declarations.
…rove code documentation
…dability and organization
…acing functionality
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title: Compliance: migrate compiler-v0.0.1 to new standard
Description:
This PR merges
new-standerdintocompiler-v0.0.1, updating the compiler and core libraries to align with the latest Helix language standard.Language Changes
Operator Declarations: switched to
fn op...()[alias]syntax.Requires Clauses: now written as
fn <params> name() requires <bounds>(old syntax still supported).Impl + Derives Shorthand:
fn <T impl Eq> name() {}Core Library Additions
std::processwithSubprocessandProcessOutput.std::systemfor command execution.std::printas an alias forprint.std::Stacktracefor runtime backtraces.std::ABI::{mangle, demangle, mangle_partial}for symbol handling.Runtime & Compiler Changes
Refactored parsing, error handling, and declaration handling to match the new syntax.
Improved mangling/demangling functions and code readability.
Added
TypeBoundrefinements and support forwherekeyword.Function declarations no longer require
?return type for panic cases:Misc Improvements
test.hlx) to comply with the new standard.Breaking Changes
Operator declarations:
op <symbol> fn <name>(...) -> <ret> {}fn op <symbol>(...)[<alias>] -> <ret> {}Requires clause change is not breaking — both old and new syntax are supported.