feat: add builtin methods

.github/linters/.markdown-link-check.json

@@ -7,7 +7,7 @@
             "pattern": "^#"
         },
         {
-            "pattern": "^https://github.com/Safe-DS/DSL/blob/main"
+            "pattern": "^https://github.com/TTSL/DSL/blob/main"
         }
     ]
 }

docs/README.md

@@ -2,4 +2,4 @@
 
 A domain-specific language (DSL) to simulate taxes and transfers.
 
-This project is based on the [Safe-DS](https://github.com/Safe-DS/DSL) DSL for statically checked Data Science programs.
+This project is based on the [TTSL](https://github.com/SEEDS-Group/TTSL) DSL for statically checked Data Science programs.

docs/development/call-graph-testing.md

@@ -5,14 +5,14 @@ graph test.
 
 ## Adding a call graph test
 
-1. Create a new file with the extension `.Tsltest` in the `tests/resources/call graph` directory or any subdirectory.
+1. Create a new file with the extension `.ttsl` in the `tests/resources/call graph` directory or any subdirectory.
    Give the file a descriptive name, since the file name becomes part of the test name.
 
     !!! tip "Skipping a test"
 
         If you want to skip a test, add the prefix `skip-` to the file name.
 
-2. Add the Safe-DS code that you want to test to the file.
+2. Add the TTSL code that you want to test to the file.
 3. Surround calls or callables for which you want to compute a call graph with test markers, e.g. `»f()«`. Add a
    comment in the preceding line with the following format:
     ```ts

docs/development/formatting-testing.md

@@ -5,17 +5,17 @@ formatting test.
 
 ## Adding a formatting test
 
-1. Create a new file with the extension `.Tsltest` in the `tests/resources/formatting` directory or any subdirectory.
+1. Create a new file with the extension `.ttsl` in the `tests/resources/formatting` directory or any subdirectory.
    Give the file a descriptive name, since the file name becomes part of the test name.
 
     !!! tip "Skipping a test"
 
         If you want to skip a test, add the prefix `skip-` to the file name.
 
-2. Add the original unformatted Safe-DS code to the top of the file. The code must be syntactically valid.
+2. Add the original unformatted TTSL code to the top of the file. The code must be syntactically valid.
 3. Add the following separator to the file:
     ```Tsl
     // -----------------------------------------------------------------------------
     ```
-4. Add the expected formatted Safe-DS code to the file below the separator.
+4. Add the expected formatted TTSL code to the file below the separator.
 5. Run the tests. The test runner will automatically pick up the new test.

docs/development/generation-testing.md

@@ -14,11 +14,11 @@ generation test.
 
         If you want to skip a test, add the prefix `skip-` to the folder name.
 
-2. Add files with the extension `.Tsltest`, `.Tslpipe`, or `.Tslstub` **directly inside the folder**. All files in a
+2. Add files with the extension `.ttsl`, `.Tslpipe`, or `.Tslstub` **directly inside the folder**. All files in a
    folder will be loaded into the same workspace, so they can reference each other. Files in different folders are
    loaded into different workspaces, so they cannot reference each other. Generation will be triggered for all files in
    the folder.
-3. Add the Safe-DS code that you want to test to the files.
+3. Add the TTSL code that you want to test to the files.
 4. If you want to run the program only up to a specific placeholder of a pipeline, surround **the name** of that
    placeholder with test markers, e.g. `val »a« = 1;`. You may only mark a single placeholder this way. Add a comment in
    the preceding line with the following format:

docs/development/grammar-testing.md

@@ -5,7 +5,7 @@ test.
 
 ## Adding a grammar test
 
-1. Create a new file with the extension `.Tsltest` in the `tests/resources/grammar` directory or any subdirectory. Give
+1. Create a new file with the extension `.ttsl` in the `tests/resources/grammar` directory or any subdirectory. Give
    the file a descriptive name, since the file name becomes part of the test name.
 
     !!! note "Naming convention"
@@ -33,7 +33,7 @@ test.
 
         By convention, the comment should be placed at the start of the file.
 
-3. Add the Safe-DS code that you want to test to the file.
+3. Add the TTSL code that you want to test to the file.
 4. Run the tests. The test runner will automatically pick up the new test.
 
 [^1]: We do not differentiate whether the error originated in the lexer (error code `lexing-error`) or the actual parser (error code `parsing-error`). Both are treated as syntax errors.

docs/development/partial-evaluation-testing.md

@@ -12,10 +12,10 @@ partial evaluation test.
 
         If you want to skip a test, add the prefix `skip-` to the folder name.
 
-2. Add files with the extension `.Tsltest` **directly inside the folder**. All files in a folder will be loaded into the
+2. Add files with the extension `.ttsl` **directly inside the folder**. All files in a folder will be loaded into the
    same workspace, so they can reference each other. Files in different folders are loaded into different workspaces, so
    they cannot reference each other.
-3. Add the Safe-DS code that you want to test to the files.
+3. Add the TTSL code that you want to test to the files.
 4. Surround entire nodes whose value you want to check with test markers, e.g. `1 + 2`.
 5. For each pair of test markers, add a test comment with one of the formats listed below. Test comments and test
    markers are mapped to each other by their position in the file, i.e. the first test comment corresponds to the first

docs/development/scoping-testing.md

@@ -12,10 +12,10 @@ test.
 
         If you want to skip a test, add the prefix `skip-` to the folder name.
 
-2. Add files with the extension `.Tsltest` **directly inside
+2. Add files with the extension `.ttsl` **directly inside
    the folder**. All files in a folder will be loaded into the same workspace, so they can
    reference each other. Files in different folders are loaded into different workspaces, so they cannot reference each other.
-3. Add the Safe-DS code that you want to test to the files.
+3. Add the TTSL code that you want to test to the files.
 4. Surround **the name** of any declaration that you want to reference with test markers, e.g. `class »C«`. Add a
    comment in the preceding line with the following format (replace `<id>` with some unique identifier):
     ```ts

docs/development/typing-testing.md

@@ -12,10 +12,10 @@ test.
 
         If you want to skip a test, add the prefix `skip-` to the folder name.
 
-2. Add files with the extension `.Tsltest` **directly inside the folder**. All files in a folder will be loaded into the
+2. Add files with the extension `.ttsl` **directly inside the folder**. All files in a folder will be loaded into the
    same workspace, so they can reference each other. Files in different folders are loaded into different workspaces, so
    they cannot reference each other.
-3. Add the Safe-DS code that you want to test to the files.
+3. Add the TTSL code that you want to test to the files.
 4. Surround entire nodes whose type you want to check with test markers, e.g. `1 + 2`. For declarations, it is also
    possible to surround only their name, e.g. `class »C«`.
 5. For each pair of test markers, add a test comment with one of the formats listed below. Test comments and test

docs/development/validation-testing.md

@@ -12,10 +12,10 @@ validation test.
 
         If you want to skip a test, add the prefix `skip-` to the folder name.
 
-2. Add files with the extension `.Tsltest`, `.Tslpipe`, or `.Tslstub` **directly inside the folder**. All files in a
+2. Add files with the extension `.ttsl`, `.Tslpipe`, or `.Tslstub` **directly inside the folder**. All files in a
    folder will be loaded into the same workspace, so they can reference each other. Files in different folders are
    loaded into different workspaces, so they cannot reference each other.
-3. Add the Safe-DS code that you want to test to the files.
+3. Add the TTSL code that you want to test to the files.
 4. Specify the expected validation results using test comments (see [below](#format-of-test-comments)) and test
    markers (e.g. `fun »F«()`). The test comments are used to specify
     * the presence or absence of an issue,

docs/language/common/aggregations.md

@@ -3,15 +3,15 @@
 To _aggregate_ [data][data] [grouped by][grouped by] an [ID][id] over a [function][functions] we can use the aggregation expression:
 
 ```ttsl
-aggregate sum of salery, taxes groupedBy hh_id
+aggregate sum of taxes groupedBy hh_id
 ```
 
 Let's break down the syntax:
 
 - The keyword `#!ttsl aggregate`.
 - The [function][functions] to be executed on the grouped values (here `#!ttsl sum`).
 - The keyword `#!ttsl of`.
-- A [List][List] of [data][data] separated by a comma (here `#!ttsl salery, taxes`).
+- The [data][data] that is aggregated (here `#!ttsl taxes`).
 - The [grouped by][grouped by] modifier (here with the id `#!ttsl hh_id`).
 
 An aggregation can be executed on one or multiple data values that are all connected to the same given [ID][id].

docs/language/common/expressions.md

@@ -48,7 +48,7 @@ In order to interpolate text with other computed values, use [template strings](
 
 ### Boolean Literals
 
-To work with truthiness, Safe-DS has the two boolean literals `#!ttsl false` and `#!ttsl true`.
+To work with truthiness, TTSL has the two boolean literals `#!ttsl false` and `#!ttsl true`.
 
 ### `#!ttsl null` Literal
 

docs/mkdocs.yml

@@ -40,8 +40,8 @@ nav:
 
 theme:
   name: material
-  logo: https://raw.githubusercontent.com/Safe-DS/.github/main/branding/safe-ds_logo_rounded.svg
-  favicon: https://raw.githubusercontent.com/Safe-DS/.github/main/branding/safe-ds_logo_rounded.svg
+  logo: https://raw.githubusercontent.com/TTSL/.github/main/branding/ttsl_logo_rounded.svg
+  favicon: https://raw.githubusercontent.com/TTSL/.github/main/branding/ttsl_logo_rounded.svg
   palette:
     # Palette toggle for light mode
     - scheme: default

packages/ttsl-cli/README.md

@@ -1,4 +1,4 @@
-# Safe-DS CLI
+# TTSL CLI
 
 ```txt
 Usage: cli [options] [command]
@@ -8,7 +8,7 @@ Options:
   -h, --help                     display help for command
 
 Commands:
-  check [options] <paths...>     check Safe-DS code
+  check [options] <paths...>     check TTSL code
   generate [options] <paths...>  generate Python code
   help [command]                 display help for command
 ```

packages/ttsl-cli/package.json

@@ -14,7 +14,7 @@
         "programming language",
         "static checking"
     ],
-    "homepage": "https://dsl.safeds.com",
+    "homepage": "https://dsl.TTSL.com",
     "bugs": {
         "url": "https://github.com/SEEDS-Group/TTSL/issues"
     },
@@ -25,7 +25,7 @@
     },
     "type": "module",
     "bin": {
-        "safe-ds": "./bin/cli.js"
+        "ttsl": "./bin/cli.js"
     },
     "exports": null,
     "files": [

packages/ttsl-cli/src/cli/check.ts

@@ -1,4 +1,4 @@
-import { createSafeDsServices } from '@ttsl/lang';
+import { createTTSLServices } from '@ttsl/lang';
 import { NodeFileSystem } from 'langium/node';
 import { extractDocuments } from '../helpers/documents.js';
 import { diagnosticToString, getDiagnostics } from '../helpers/diagnostics.js';
@@ -7,7 +7,7 @@ import chalk from 'chalk';
 import { ExitCode } from './exitCode.js';
 
 export const check = async (fsPaths: string[], options: CheckOptions): Promise<void> => {
-    const services = (await createSafeDsServices(NodeFileSystem)).SafeDs;
+    const services = (await createTTSLServices(NodeFileSystem)).TTSL;
 
     let errorCount = 0;
 

packages/ttsl-cli/src/cli/exitCode.ts

@@ -18,9 +18,9 @@ export enum ExitCode {
     NotAFileOrDirectory = 101,
 
     /**
-     * The given file does not have a Safe-DS extension.
+     * The given file does not have a TTSL extension.
      */
-    FileWithoutSafeDsExtension = 102,
+    FileWithoutTTSLExtension = 102,
 
     /**
      * The given file has errors.

packages/ttsl-cli/src/cli/format.ts

@@ -1,4 +1,4 @@
-import { createSafeDsServices } from '@ttsl/lang';
+import { createTTSLServices } from '@ttsl/lang';
 import { NodeFileSystem } from 'langium/node';
 import { extractDocuments } from '../helpers/documents.js';
 import { exitIfDocumentHasSyntaxErrors } from '../helpers/diagnostics.js';
@@ -7,7 +7,7 @@ import { writeFile } from 'node:fs/promises';
 import chalk from 'chalk';
 
 export const format = async (fsPaths: string[]): Promise<void> => {
-    const services = (await createSafeDsServices(NodeFileSystem)).SafeDs;
+    const services = (await createTTSLServices(NodeFileSystem)).TTSL;
     const documents = await extractDocuments(services, fsPaths);
 
     // Exit if any document has syntax errors before formatting code
@@ -31,5 +31,5 @@ export const format = async (fsPaths: string[]): Promise<void> => {
         await writeFile(document.uri.fsPath, editedDocument);
     }
 
-    console.log(chalk.green(`Safe-DS code formatted successfully.`));
+    console.log(chalk.green(`TTSL code formatted successfully.`));
 };

packages/ttsl-cli/src/cli/generate.ts

@@ -1,4 +1,4 @@
-import { createSafeDsServices } from '@ttsl/lang';
+import { createTTSLServices } from '@ttsl/lang';
 import chalk from 'chalk';
 import { URI } from 'langium';
 import { NodeFileSystem } from 'langium/node';
@@ -9,7 +9,7 @@ import { makeParentDirectoriesSync } from '../helpers/files.js';
 import { exitIfDocumentHasErrors } from '../helpers/diagnostics.js';
 
 export const generate = async (fsPaths: string[], options: GenerateOptions): Promise<void> => {
-    const services = (await createSafeDsServices(NodeFileSystem)).SafeDs;
+    const services = (await createTTSLServices(NodeFileSystem)).TTSL;
     const documents = await extractDocuments(services, fsPaths);
 
     // Exit if any document has errors before generating code

packages/ttsl-cli/src/cli/main.ts

@@ -17,14 +17,14 @@ program
     .command('check')
     .argument('<paths...>', `list of files or directories to check`)
     .option('-s, --strict', 'whether the program should fail on warnings', false)
-    .description('check Safe-DS code')
+    .description('check TTSL code')
     .action(check);
 
 // Format command
 program
     .command('format')
     .argument('<paths...>', `list of files or directories to format`)
-    .description('format Safe-DS code')
+    .description('format TTSL code')
     .action(format);
 
 // Generate command

packages/ttsl-cli/src/helpers/documents.ts

@@ -31,13 +31,13 @@ export const extractDocuments = async function (
 };
 
 /**
- * Processes the given paths and returns the corresponding URIs. Files must have a Safe-DS extension. Directories are
+ * Processes the given paths and returns the corresponding URIs. Files must have a TTSL extension. Directories are
  * traversed recursively.
  *
  * @returns The URIs of the matched files.
  */
 export const processPaths = (services: LangiumServices, fsPaths: string[]): Result<URI[], ProcessPathsError> => {
-    // Safe-DS file extensions
+    // TTSL file extensions
     const extensions = services.LanguageMetaData.fileExtensions;
     const pattern = `**/*{${extensions.join(',')}}`;
 
@@ -55,11 +55,11 @@ export const processPaths = (services: LangiumServices, fsPaths: string[]): Resu
         // Path must be a file or directory
         const stat = fs.lstatSync(fsPath);
         if (stat.isFile()) {
-            // File must have a Safe-DS extension
+            // File must have a TTSL extension
             if (!extensions.includes(path.extname(fsPath))) {
                 return Result.err({
-                    message: `File '${fsPath}' does not have a Safe-DS extension.`,
-                    code: ExitCode.FileWithoutSafeDsExtension,
+                    message: `File '${fsPath}' does not have a TTSL extension.`,
+                    code: ExitCode.FileWithoutTTSLExtension,
                 });
             }