ValueScript icon indicating copy to clipboard operation
ValueScript copied to clipboard

A dialect of TypeScript with value semantics.

Results 9 ValueScript issues
Sort by recently updated
recently updated
newest added

ValueScript is free and open source. We want it to be guided by community feedback. Comment here for small things or questions about giving substantial feedback. If you have something...

good first issue
no coding

Diagnostics are errors/lints/etc that the toolchain emits when processing input. Like this: ``` ➜ ValueScript git:(main) vstc run inputs/passing/captureMutated.ts inputs/passing/captureMutated.ts:2:7: Lint: `x` should be declared using `const` because it is...

good first issue
no coding

I'm curious to find out how small of a device we can run ValueScript on. Raspberry pi pico? Arduino? An extended version of this would be to add a new...

good first issue

ValueScript has a variety of concept code in [concept-code](https://github.com/voltrevo/ValueScript/tree/main/concept-code). This is code that (at least when it was written), didn't work. The idea is to be extremely specific about the...

good first issue

We need more programs showcasing what ValueScript can do. If your program is relatively small, consider including it in `inputs/passing` and add the `test_output` header. Otherwise, add a link to...

good first issue

I'd like files in `inputs/**` to be able to be annotated with diagnostics for automated testing, similar to how `test_output!` works. For example, I'd like to be able to change...

good first issue

Input test cases for ValueScript are really simple. All you have to do is write a program like this: ```ts // test_output! "Hello world!" export default function() { return "Hello...

good first issue

I've been learning rust as I've been building ValueScript. I'm getting better, but I'm sure the code would still benefit by being rustier in many places. At minimum, `cargo clippy`...

good first issue

https://github.com/voltrevo/ValueScript/issues/1 demonstrates a program which behaves incorrectly. Solving this wouldn't be a good first issue, but adding a failing test case for it is. All you have to do is...

good first issue