DotGet function calls #9

defunkt · 2025-10-26T23:29:58Z

defunkt commented

2025-10-26 23:29:58 +00:00

This does a few things.

It makes DotGet act more like Identifier where this:

config.path

Is (potentially) a function call. Just like this would be:

config-path

It also works with args, naturally:

io.print Heya

It updates scope detection by adding a do keyword and using that to determine if we're in a FunctionDef scope (fixes a bug)
It allows numbers to be used in DotGet:

$ cat oh.sh
nums = list 1 2 3
echo Index one is nums.1
$ ./bin/shrimp oh.sh
Index one is 2

This does a few things. 1. It makes `DotGet` act more like `Identifier` where this: `config.path` Is (potentially) a function call. Just like this would be: `config-path` It also works with args, naturally: `io.print Heya` 2. It updates scope detection by adding a `do` keyword and using that to determine if we're in a `FunctionDef` scope (fixes a bug) 3. It allows numbers to be used in `DotGet`: ``` $ cat oh.sh nums = list 1 2 3 echo Index one is nums.1 $ ./bin/shrimp oh.sh Index one is 2 ```

defunkt added 1 commit 2025-10-26 23:29:58 +00:00

DotGet function calls abd7d2e43b

defunkt added 1 commit 2025-10-27 05:23:52 +00:00

update params scope detection, add array.1 (dotget array indices) 972fd25fda

defunkt added 1 commit 2025-10-27 05:32:11 +00:00

compile dot number too 219142140c

probablycorey commented

2025-10-27 19:45:23 +00:00

Love it

probablycorey added 2 commits 2025-10-27 19:46:03 +00:00

Merge remote-tracking branch 'origin/main' into dotget-function-calls ffdd666685

Update shrimp.ts 318142dfbb