Make all CallOrTree expressions breakable

.codecov.yml

@@ -0,0 +1,11 @@
+coverage:
+  precision: 0
+  status:
+    project:
+      default:
+        # basic
+        target: auto
+        threshold: 1% # we accept a bit fluctuation, as we run random tests
+        base: auto 
+        paths: 
+          - "src"

.git-blame-ignore-revs

@@ -0,0 +1,12 @@
+# List of commits that shouldn't be included in `git blame`. 
+# Github and other tools already support it if it's this exact filename
+# But you have to teach your own git about this by running this command (in this repo)
+# git config blame.ignoreRevsFile .git-blame-ignore-revs
+
+# indent fix for JSON
+31b1031ade5d84f9c60e30d17da3b55e78d291fb
+
+# fixing tabs & spaces mixed
+0d048e15683740b5c944be5333ec0680df825e47
+23ec4b622bbe503ef013be5a458e45ae6fd89b97
+200b0352084be9435c64aa60c550edd24a59131b

.gitattributes

@@ -0,0 +1 @@
+*.dot diff=-astextplain

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+
+Steps to reproduce the behavior:
+1. Modules to define (attach files or inline code quotes)
+2. REPL commands to type
+3. AND/OR: Eclipse IDE actions to trigger
+4. See error in? REPL, Error Log, Console log?
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Stack traces**
+
+Literally copy stacktraces from the console, or from the Eclipse Error log here.
+
+**Desktop (please complete the following information):**
+ - Context: Eclipse plugin, Commandline REPL
+ - Rascal Version [e.g. 0.17.0], stable or unstable release?
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature 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.

.github/ISSUE_TEMPLATE/stable-release-manual-testing-template.md

@@ -0,0 +1,90 @@
+---
+name: Stable release manual testing template
+about: This is a list of things to do and to check at the time of a stable release
+title: "[RELEASE] version 0.x.x"
+labels: release testing
+assignees: ''
+
+---
+
+# Preliminaries
+
+* Every time this document says "release X" ; we mean to execute the instructions of this Wiki page: https://github.com/usethesource/rascal/wiki/How-to-make-a-release-of-a-Rascal-implemenation-project
+* The current release instructions are focused on the Rascal commandline tools and the Eclipse IDE plugin
+* If you edit this template, then please push relevant improvements to the template itself for future reference.
+
+# Pre-releasing dependent tools in unstable
+
+First a "pre-release" of the supporting compiler/typechecker tools must be done, so we know we are releasing a consistently compiled standard library.
+
+- [ ] typepal and rascal-core compile in the continuous integration environment and no tests fail
+- [ ] release typepal
+- [ ] release rascal-core
+- [ ] bump typepal and rascal-core versions in rascal-maven-plugin to latest releases
+- [ ] bump typepal and rascal-core versions in rascal-eclipse to latests SNAPSHOT releases
+- [ ] release rascal-maven-plugin
+- [ ] bump rascal-maven-plugin dependency in rascal and rascal-eclipse project
+- [ ] fix new errors and warnings in rascal and rascal-eclipse project
+
+# Manual version checks
+
+- [ ] Continuous Integration runs all unit and integration tests and fails no test
+- [ ] Maximum number of compiler warnings are resolved
+- [ ] Version numbers are verified manually
+
+# Manual feature tests
+
+- [ ] Eclipse download and install latest unstable release from update site https://releases.usethesource.io/maven/org/rascalmpl/rascal-update-site/
+- [ ] Open a Rascal REPL using the toolbar button
+- [ ] Can create new Rascal project using the wizard
+- [ ] Can create new Rascal module using the wizard
+- [ ] Can edit Rascal file in Rascal project
+- [ ] Save on Rascal file triggers type-checker
+- [ ] Rascal outline works
+- [ ] Rascal navigator works
+- [ ] Rascal navigator displays working sets
+- [ ] Rascal navigator displays interpreter's search path
+- [ ] Clicking links in REPL opens editors and websites
+- [ ] `rascal>1 + 1` on the REPL
+- [ ] `import IO; println("Hello Rascal!");`
+- [ ] in editor, click on use of name jumps to definition
+- [ ] jump-to-definition also works to library modules and inside library modules
+- [ ] clicking in outline jumps to editor to right position
+- [ ] syntax highlighting in editor works
+- [ ] add dependency on another project by editing `pom.xml` `<dependencies> tag, import a module and test the type-checker as well as the interpreter for correct resolution
+- [ ] `import demo::lang::Pico::Plugin; registerPico();` and test the editor of the example pico files (syntax highlighting, menu options)
+- [ ] `import demo::lang::Pico::Plugin; rascal>:edit  demo::lang::Pico::Plugin`
+- [ ] use util::IDEServices:
+   - [ ] registerDiagnostics with more than one file
+   - [ ] test edit function (for example with vis::Graph examples that use it)
+   - [ ] test showInteractiveContent function (for example with vis::Chart examples)
+
+# Actual release
+
+- [ ] release rascal project (when resolving SNAPSHOT dependencies choose the right versions of vallang etc, and make sure to bump the new rascal SNAPSHOT release one minor version)
+- [ ] bootstrap documentation site
+   - [ ] bump rascal version in rascal-maven-project, mvn install
+   - [ ] bump rascal version in rascal-website project
+   - [ ] set rascal-maven-project snapshot dependency in rascal-website project
+   - [ ] run `mvn clean package` in rascal-website project
+   - [ ] fix errors, possibly release rascal project patch versions, and repeat the above.
+   - [ ] release rascal-maven-project
+   - [ ] bump rascal-maven-project dependency in rascal-website project
+   - [ ] run `mvn clean package` in rascal-website project and `git push` to publish new docs
+- [ ] release rascal-eclipse project (take care to choose the right release versions of typepal and rascal-core you release earlier and choose their new SNAPSHOT dependencies to the latest)
+- [ ] change the configuration of the stable version in `update-site-nexus-link-script/refresh-nexus-data` to the released version
+- [ ] test the stable update site at https://update.rascal-mpl.org/stable
+- [ ] write release notes and publish on the usethesource.io blog
+
+# Downstream implications
+
+The following items can be executed asynchronously, but are nevertheless not to be forgotten:
+
+- [ ] change dependencies on rascal-eclipse and rascal in rascal-eclipse-libraries and the projects it depends on
+- [ ] change dependencies of typepal to latest rascal and rascal-eclipse
+- [ ] change dependency of rascal-core to latest stable rascal
+- [ ] change dependency in all projects on new rascal-maven-project
+- [ ] change dependency of rascal-maven-project and rascal in rascal-tutor
+- [ ] release rascal-tutor
+- [ ] bump dependency of rascal-tutor in rascal-maven-project
+- [ ] release rascal-maven-project again