Well this is pretty great. My only feedback, and i'm sure you're working on it, would be a wiki with slang syntax and specific documentation. I can get around cause i'm familiar with C based languages, but having a resource like the in game list of variables and functions would be helpful.

I could probably also work on some "context awareness" in the compiler to see if you are trying to pass a string into a batched function and automatically hash it for you

As for functions, I'm working on doing a code refactor of the tokenizer right now. When that's done and I get the rest of the IC10 built-in functions in, I'll work on fixing up the ABI for functions :)

Thanks for trying Slang!

So IC10 really doesn't have a concept of "Strings". So in Slang if you want to use a string you generally are going to want to use the `hash("SomeString")` function. As of _now_ LogicTypes and other things _are_ handled as strings in Slang.

Such as:

[code]
const solarPanels = hash("StructureSolarPanelDual");

lbn(solarPanels, "Charge", "Sum");
[/code]

In the future I will be strongly typing the structure names, logic types, and batch modes so that autocomplete works as intended and misuse will cause compiler errors in game :)

hey, congrats on the beta release! i really really love using this. it's reduced the friction and slimmed the difficulty curve of getting into stationeers coding for me quite significantly. the same tasks that I was shooting for took less than half the time because of how approachable this is.

i think you mention it somewhere in the stationpedia where functions don't quite work as intended and i'm noticing that as well (various issues with scope-awareness and variable usage). i'm really excited for when this fully implemented!

i also couldn't figure out if there was a way to set strings or really use strings at all yet? looking forward to the feature parity for IC10.

thanks so much for making this and i hope you continue to work on it!