To do :

• #121
• #120
• #119
• #118
• #117

(print (+ (- (* 4 3) (/ 6 3)) 5))

This code results in the following error:

glados: Function -: args are not Atoms

This issue aims to resolve the issue presented in the integrationTests/TestFiles/Factorial.scm test file where because we evaluate the arguments of the if function before evaluating the if condition, if we have recursive calls we will recurse infinitely.

To do

• #123
• #122
• #129
• #130
• #131

add builtins to read from standard input / output

read -> returns (RetVal Registry Ast.Literal)
readNum -> returns (RetVal Registry Ast.Literal)

This issue tracks:

• Conversion of parsing to standalone library
• VSCode test syntax highlighting fix
• No other VSCode issue

Write a Syntax description for our Scheme derivate.
We will be using the Augmented Backus Naur form.

• add feature request template
• add license

Update the readme with up to date information

Purpose

This issue serves the purpose of updating the build system in order to produce :

• A "compiler" binary
• A "execution environment" binary

Describe the solution you'd like

(define (add a b) (+ a b))
(a `add` b)

or

(3 `eq?` 2)

Should be valid expressions.
If a function is surrounded by inclined quotation marks ` it is supposed to be called as an infix function with the lowest priority level.
This means that infix functions can only be called with exactly 2 arguments.

Goal

The goal of this issue is to implement the basic features of compileExpr (none of the more advanced features that reference detailed parts of the compileExpr).

Describe the solution you'd like
It should be possible to write an Ast.Expr to a file or to append an Ast.Expr to a file ny transforming it into a string using the show function

• add function comments
• fix -i flag not working

Describe the solution you'd like
describe the following syntaxes:

• arrays
• infix syntax call
• 0 arguments

Gestion for our languages with stack

The goal of this issue is to improve the readability and rigor of the tests in our test suite.

This means :

• Put input and assertion values in variables for increased readability
• Make sure test is not redundant and correct
• Ensure you are declaring the least variables possible (try to reuse input values for previous tests where possible)
• Check test name (simplify where possible)

Files to cleanup :

• ArgsTests.hs -> @nLatt
• AstTests.hs -> @mindoodoo
• CptTests.hs -> @mindoodoo
• TokenTests.hs -> @virgile-crtl
• ExecTests.hs -> @virgile-crtl
• ParsingTests.hs -> @audetuczapski
• TestMain.hs -> @bilou931

To do :

• Implement Stack and Function Execution
• Stack frame should contain :
  • Return pointer
  • Arguments bound to variable names
  • Resume offset

Describe the solution you'd like
Add support for float operations

Purpose

Update exception handling to reflect switch to a semi "compiled" language. Two exception types need to be implemented :

• Compilation Exceptions
• Runtime Exceptions

Describe the solution you'd like
It should be possible to use arrays and they should be wrapped by syntactic sugar to give a syntax like that:

[1, 2, 3]

Additional context
Add any other context or screenshots about the feature request here.

• #105
• #106
• #107
• #111
• #112
• #113
• #114
• #115

Describe the solution you'd like
It should be possible to read the contents of a file and return it as an Ast.Literal

Main parsing of the interpreter

This issue will track the development of the main parsing components that will then allow the efficient execution of the code.

Todo :

• Tokenization
• Parse tokens into Concrete Parse Tree
• Translate CPT into Abstract Syntax Tree

• #133

Basic Documentation

The goal of this issue is to write basic documentation for the scheme language and for the main components of our library / interpreter.

Checklist :

• Check relevence of all comments
• Readme.md
  • Table of contents
  • Installation
  • Building
  • Misc
  • Badges (to make it pretty hehe)
• Contributing.md
  • Style
  • Commitizen
  • PR Workflow

• Load files via stdin

$ ./glados < test.scm

• Load files via flag

$ ./glados -f test.scm
$ ./glados --file test.scm

• launch repl

./glados
> (+ 3 2)

Additional flags:

• -d --debug: stops at each scope change and waits for an enter keypress

The goal of this issue is to implement a custom instance (as opposed to simply deriving it) of the Show typeclass for the RuntimeException data type.

By doing so, we will be able to "pretty" print the exceptions as soon as we catch them.