epoch-language
epoch-language copied to clipboard
Home of the Epoch Programming Language Project
This issue is a meta tracking issue for all work related to self-hosting the Epoch compiler on 64-bit Windows. While the 32-bit compiler has been self-hosted for some time, our...
Populate the types data in the PDBs when it becomes practical.
``` if(something()) { integer foo = 42 } else { foo = 666 } This nonsense compiles and executes, albeit with undefined behavior. Fix scoping rules to be enforced properly....
``` Fix the LLVM code generated by operators that need to short-circuit (i.e. && and || for now). ``` Original issue reported on code.google.com by `[email protected]` on 5 Sep 2014...
``` Compilation can proceed blindly and attempt to generate code based on faulty input (i.e. code with type errors). ``` Original issue reported on code.google.com by `[email protected]` on 5 Sep...
``` Review code for chained assignments, particularly ones involving compound operands, and make sure all edge cases are handled correctly. Unit tests should be written to help confirm this in...
``` Code blocks with no prefix keyword are currently not supported. ``` Original issue reported on code.google.com by `[email protected]` on 5 Sep 2014 at 5:29
``` Assignment operations are not properly type checked. Both trivial and compound Left-Hand-Side assignments need to be type checked. ``` Original issue reported on code.google.com by `[email protected]` on 5 Sep...
``` It is not enforced that all type-match or pattern-match overloads return the same type. This can cause bogosity. Add type safety checks to ensure either: - All overloads return...
``` Identifier shadowing is currently not detected/prohibited correctly by the Epoch compiler. ``` Original issue reported on code.google.com by `[email protected]` on 5 Sep 2014 at 5:26