Repository: Para-Lang/para-compiler (language: python)

Issue:
List removal patch 1
## Summary
Merging list-type changes, which include the removal of the `list<t>` type and the merge of 

## Introduced Changes
Removed `list<t>` from the `ParaC.g4` grammar file and updated the .docx file.

## Is this PR related to an issue or problem
No.

## Does your new code introduce new warnings or errors? (At current state)
No.

## Changelog

### Added
- Merged dynamic lists and arrays into the standard iterable type associated with `type identifier[]`,
  which can utilise list functionality, but also practically stay normal arrays at the same time if not resized. For 
  more info see the lang document.
- Python Path Modification in `src/pytest/conftest.py` to fix local pytest issue on Windows
- In `.docx` file section for `iterable`

### Removed
- `list<t>` type from the Grammar file




Discussion / hints:

Fix patch:
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 00000000..9aacfe53
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a report to help us improve and report an issue
+title: "[Bug] ..."
+labels: bug, question
+assignees: Luna-Klatzer
+
+---
+
+<!---
+Note that any issue that does not follow this style, or does not contain the info filled out, will NOT be checked. It should contain every information the first time posting. 
+
+Asking for info takes time that is unnecessarily wasted if it's not correctly posted here!
+-->
+
+**Describe the bug**
+
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+
+Steps to reproduce the behaviour:
+1. Go to '...'
+2. Utilise/Call '...' with param '...'
+3. See error
+
+**Expected behaviour**
+
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. Win, Ubuntu, Arch, MacOS]
+ - Runtime Version: [Python module/Compiled binary]
+ - Installation Type: [Win-Installer/Self-build/Pip-Module]
+ - Version: [e.g. 0.1]
+
+**Additional context**
+
+Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 00000000..83c84308
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,43 @@
+---
+name: Feature Proposal
+about: Suggest an idea for this project
+title: "[Feature Proposal] ..."
+labels: enhancement proposal
+assignees: Luna-Klatzer
+
+---
+
+<!---
+Note that any issue that does not follow this style, or does not contain the info filled out, will NOT be checked. It should contain every information the first time posting. 
+
+Asking for info takes time that is unnecessarily wasted if it's not correctly posted here!
+-->
+
+**Affected area by change:**
+- Compiler Source Code: [yes/no]
+- Pre-Processor Source Code: [yes/no]
+- `parac` parent module: [yes/no]
+- CLI: [yes/no]
+- Inno-Installer (Win): [yes/no]
+- Documentation: [yes/no]
+
+**Short Introduction and Summary**
+<!---
+Please keep it short and only add important info. Afterwards, add in the other items clearer and detailed info.
+-->
+
+**Is your request related to a problem? Please describe.**
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+
+Add any other context or screenshots about the feature request here.
diff --git a/.github/ISSUE_TEMPLATE/interface--tool-or-cli-request.md b/.github/ISSUE_TEMPLATE/interface--tool-or-cli-request.md
new file mode 100644
index 00000000..33c3f621
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/interface--tool-or-cli-request.md
@@ -0,0 +1,42 @@
+---
+name: Interface, Tool or CLI Proposal
+about: Suggest an idea for the interface, Compiler tools or CLI.
+title: "[Tool Proposal] ..."
+labels: enhancement proposal
+assignees: Luna-Klatzer
+
+---
+
+<!---
+Note that any issue that does not follow this style, or does not contain the info filled out, will NOT be checked. It should contain every information the first time posting. 
+
+Asking for info takes time that is unnecessarily wasted if it's not correctly posted here!
+-->
+
+**Affected area by change:**
+- Python module: [yes/no]
+- Python Plugins: [yes/no]
+- Project Structure or Para-C Make: [yes/no]
+- CLI: [yes/no]
+- Inno-Installer (Win): [yes/no]
+
+**Short Introduction and Summary**
+<!---
+Please keep it short and only add important info. Afterwards, add in the other items clearer and detailed info.
+-->
+
+**Is your request related to a problem? Please describe.**
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+
+Add any other context or screenshots about the feature request here.
diff --git a/.github/ISSUE_TEMPLATE/language-enhancement-request.md b/.github/ISSUE_TEMPLATE/language-enhancement-request.md
new file mode 100644
index 00000000..cc25dba2
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/language-enhancement-request.md
@@ -0,0 +1,41 @@
+---
+name: Language Enhancement Proposal
+about: Suggest an idea for this project
+title: "[Lang Enhancement Proposal] ..."
+labels: enhancement proposal
+assignees: Luna-Klatzer
+
+---
+
+<!---
+Note that any issue that does not follow this style, or does not contain the info filled out, will NOT be checked. It should contain every information the first time posting. 
+
+Asking for info takes time that is unnecessarily wasted if it's not correctly posted here!
+-->
+
+**Affected area by change:**
+- Language Syntax: [yes/no]
+- Language Library (Parac Base Library); [yes/no]
+- Pre-Processor: [yes/no]
+- Documentation: [yes/no]
+
+**Short Introduction and Summary**
+<!---
+Please keep it short and only add important info. Afterwards, add in the other items clearer and detailed info.
+-->
+
+**Is your request related to a problem? Please describe.**
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+
+Add any other context or screenshots about the feature request here.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..ef9b6d1a
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,34 @@
+## Summary
+<!---
+Explain the reason for this pr, changes and solution briefly.
+-->
+
+## Introduced Changes
+<!---
+Please explain the introduced changes and how they matter
+-->
+
+## Is this PR related to an issue or problem
+<!---
+For example a github issue or a general problem
+-->
+
+## What was the root cause for the problem
+<!---
+Please explain the root cause of the problem. Remove if unnecessary 
+-->
+
+## Does your new code introduce new warnings or errors? (At current state)
+<!---
+CodeQL, Tests and while running
+-->
+
+## Changelog
+<!---
+Changelog, which explains new additions or changes. Minor changes should only
+be included if they matter or have a big influence on the code/project
+-->
+
+### Added
+### Changed
+### Removed
\ No newline at end of file
diff --git a/.github/workflows/codeql-analysis.yml b/.github/workflows/codeql-analysis.yml
new file mode 100644
index 00000000..7159570c
--- /dev/null
+++ b/.github/workflows/codeql-analysis.yml
@@ -0,0 +1,41 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [ main ]
+  schedule:
+    - cron: '20 15 * * 1'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'python' ]
+        
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v2
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v1
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+        # queries: ./path/to/local/query, your-org/your-repo/queries@main
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v1
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2dd3ff82..37ca08ec 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,8 +12,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 ### Changed
+- Merged dynamic lists and arrays into the standard iterable type associated with `type identifier[]`,
+  which can utilise list functionality, but also practically stay normal arrays at the same time if not resized. For 
+  more info see the lang document.
 
 ### Removed
+- `list<t>` type from the Grammar file
 
 ## [v0.1.dev4] - 2021-07-23
 
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..056d8947
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,129 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive and useful feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience. This can also include trying to fix mistakes
+  and making up for them
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+luna.klatzer@gmail.com (Project Maintainer).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
diff --git a/doc/ParaC-Luna-Klatzer.docx b/doc/ParaC-Luna-Klatzer.docx
index f5eb505b..cf01f796 100644
Binary files a/doc/ParaC-Luna-Klatzer.docx and b/doc/ParaC-Luna-Klatzer.docx differ
diff --git a/grammar/ParaC.g4 b/grammar/ParaC.g4
index 06ef2031..cf25bbef 100644
--- a/grammar/ParaC.g4
+++ b/grammar/ParaC.g4
@@ -226,7 +226,6 @@ typeSpecifier
     |   'float'
     |   'double'
     |   'signed'
-    |   'list' '<' typeSpecifier '>'
     |   'lambda' '<' parameterTypeList '>'
     |   'unsigned'
     |   '_Bool'
@@ -412,7 +411,7 @@ typedefName
 
 initializer
     :   assignmentExpression
-    |   '{' initializerList ','? '}'
+    |   '{' initializerList? ','? '}' // array
     ;
 
 initializerList
@@ -594,7 +593,6 @@ If : 'if';
 Inline : 'inline';
 Int : 'int';
 Lambda : 'lambda';
-List : 'list';
 Long : 'long';
 Register : 'register';
 Restrict : 'restrict';
diff --git a/src/parac/preprocessor/python/ParaCPreProcessorLexer.py b/src/parac/preprocessor/python/ParaCPreProcessorLexer.py
index e755e9ef..c47604bc 100644
--- a/src/parac/preprocessor/python/ParaCPreProcessorLexer.py
+++ b/src/parac/preprocessor/python/ParaCPreProcessorLexer.py
@@ -1,4 +1,3 @@
-# coding=utf-8
 # Generated from ./grammar/ParaCPreProcessor.g4 by ANTLR 4.9.2
 from antlr4 import *
 from io import StringIO
diff --git a/src/parac/preprocessor/python/ParaCPreProcessorListener.py b/src/parac/preprocessor/python/ParaCPreProcessorListener.py
index 329eebc7..f175ffd4 100644
--- a/src/parac/preprocessor/python/ParaCPreProcessorListener.py
+++ b/src/parac/preprocessor/python/ParaCPreProcessorListener.py
@@ -1,4 +1,3 @@
-# coding=utf-8
 # Generated from ./grammar/ParaCPreProcessor.g4 by ANTLR 4.9.2
 from antlr4 import *
 if __name__ is not None and "." in __name__:


Test patch:
diff --git a/src/pytest/.coveragerc b/src/pytest/.coveragerc
index d09f6078..b114b811 100644
--- a/src/pytest/.coveragerc
+++ b/src/pytest/.coveragerc
@@ -1,5 +1,5 @@
 [run]
-source = ../parac
+source = ../
 omit =
    *\pkg_resources\*
    *\out\*
diff --git a/src/pytest/conftest.py b/src/pytest/conftest.py
index 780d4f16..4e06769e 100644
--- a/src/pytest/conftest.py
+++ b/src/pytest/conftest.py
@@ -1,10 +1,17 @@
 # coding=utf-8
 """ Configuration file for pytest """
+import os
+import shutil
 import sys
+from pathlib import Path
+
 import pytest
 import logging
-import parac
 
+p = Path("..").absolute()
+sys.path.append(str(p))
+
+import parac
 parac.RUNTIME_COMPILER.init_logging_session(
     level=logging.DEBUG, print_banner=False
 )
diff --git a/src/pytest/test_files/lambda.para b/src/pytest/test_files/lambda.para
index 436b1e58..13fd307c 100644
--- a/src/pytest/test_files/lambda.para
+++ b/src/pytest/test_files/lambda.para
@@ -3,6 +3,7 @@ entry status Main()
     lambda<int> multiply_by_two = (int x) => x * 2;
     lambda<int> func = ((int x) => x as int) as lambda<int>;
     lambda<int, int > func2 = (int x, int y) => (int) x * y;
+    lambda<int, y, z, ...> x = 3; // will raise an error
 
     return (status) { .status_code = 0 };
 }
\ No newline at end of file