- Lost in the World Wide Web (help)
- https://schrottkatze.de
- Joined on
2023-05-03
I think it makes sense for debugging purposes. Or do you plan to add a way to be able to output the IR to a more readable form of IR (that has a similar syntax, similar to the human readable forms…
I do not see how this is related to Variant at all.
Variant is the internal way to store data, yes?
And that must be able to store more data then an image buffer or a few numbers or…
you dont always wanna give all parameters to a noise generator for example kinda want a system for named args but i have no idea how to implement that in the language lol
Ahh okay! I meant more sinks/consumers
and potentially for write to also be able to write csvs etc
Ok seriously we probably need to have a meeting and talk about the terminology ^^' this is really becoming a headache and a mess
Is this the note that was referred to in the other file? Or the one inside the struct?
And for development probably later on as well, though the runtime/server/whatever should be able to provide enough info to do that comfortably as well.
I'm going to rework this to be much more statically typed, but for now this should be fine.
note to keep in mind for later, maybe this should also have the option to have default values? probably rather relevant for frontends...
I generally prefer using to_owned, since it's more clear that you're turning an unowned string (&str) into an owned String.
One general note (mostly for later, which I'll work on in the next few days): The runtime should be able to mix and match executors, so one executor may not fully support all instructions but for that offer more performance (because some shit might be harder to implement as compute shaders) so switching on the fly is possible.