You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jmeaster30 opened this issue
Aug 11, 2023
· 3 comments
Labels
BytecodeStuff dealing with the hydro bytecodeFeaturethis is something we need to addHydroConcerns with the Hydro languageLexerchange with the lexingParserchange with the parserUHOHthis is a bug
We don't currently support string and char variables but it would be nice to allow someone to type out a string and have it represent a u8 array. If it is a single byte then it represents a u8 instead.
Also we currently produce a string when we are pushing an identifier for indexing.
I think we should make an access instruction that has a built in identifier in it instead of relying on the index instruction. Splitting them up will probably make the code a little simpler too.
BytecodeStuff dealing with the hydro bytecodeFeaturethis is something we need to addHydroConcerns with the Hydro languageLexerchange with the lexingParserchange with the parserUHOHthis is a bug
Realized there is no need for strings specifically and we can just use Unsigned8s in an Array to get the same effect
The text was updated successfully, but these errors were encountered: