Merge remote-tracking branch 'fork/production' into Gleam

This commit is contained in:
Lunarmagpie 2023-03-08 03:19:58 -05:00
commit 4bb58bac57
19 changed files with 106 additions and 37 deletions

View file

@ -10,7 +10,7 @@ In the example of NodeJS, we would call this `node`, after the main binary.
See [deno/1.7.5/](deno/1.7.5/) or any other directory for examples.
1. Create a new branch on your fork of engineer-man/piston
1. Create a new branch on your fork of endercheif/piston
2. Create directories named `[language]/[version]`. See Naming Languages for how to determine the name for your language

View file

@ -1 +1 @@
python3 -m samarium $1
python3 -m samarium $1

3
packages/samarium/0.4.0/build.sh vendored Executable file
View file

@ -0,0 +1,3 @@
#!/bin/bash
source ../../python/3.10.0/build.sh
bin/pip3 install https://github.com/samarium-lang/Samarium/archive/refs/tags/0.4.0.zip

2
packages/samarium/0.4.0/environment vendored Normal file
View file

@ -0,0 +1,2 @@
#!/bin/bash
export PATH=$PWD/bin:$PATH

5
packages/samarium/0.4.0/metadata.json vendored Normal file
View file

@ -0,0 +1,5 @@
{
"language": "samarium",
"version": "0.4.0",
"aliases": ["sm"]
}

1
packages/samarium/0.4.0/run vendored Normal file
View file

@ -0,0 +1 @@
python3 -m samarium $1

3
packages/samarium/0.4.0/test.sm vendored Normal file
View file

@ -0,0 +1,3 @@
=> * {
"OK"!;
}