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 full hierarchy useful in IR land? I guess it might make sense to have a statement/expression level, but for transformations we may want to do are the pipeline/pipeline elemen hierarchies still as useful. (e.g. if we want to lift a | get bla to a direct cell path access etc.
Lifting | get bla to a direct cell path access would require get to be a parser keyword (or done later via some IR optimization?). I haven't looked closely to the IR yet, so I can't tell if it would be better with or without pipelines, but we'll need some way to track command inputs/outputs. We'll also need it at the AST level to parse and typecheck it properly.
Currently, pipelines and pipeline elements are missing. In Nushell the hierarchy is
while we have only
The text was updated successfully, but these errors were encountered: