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
Is this out of scope for the compiler? Should it be a separate project which uses huck as a Rust library?
For this, we'll need to cache the type of every single ast node, so that we can find out exactly the type of any expression, regardless of where it appears, or whether it's named or not. To support this, we probably want to change most ast nodes to be {} structs and variants, because tuple structs will be obnoxious to use with a () argument everywhere.
The text was updated successfully, but these errors were encountered:
Is this out of scope for the compiler? Should it be a separate project which uses
huck
as a Rust library?For this, we'll need to cache the type of every single
ast
node, so that we can find out exactly the type of any expression, regardless of where it appears, or whether it's named or not. To support this, we probably want to change mostast
nodes to be{}
structs and variants, because tuple structs will be obnoxious to use with a()
argument everywhere.The text was updated successfully, but these errors were encountered: