We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently we have
pipe([out.Y], out.X) -> Namespace(Y=<branch output>, X=<main output>)
which is great, but then
pipe([out.X], out.X) -> Namespace(X=(<branch output>, <main output>))
which is not so good.
You might say "so don't use the same output name twice in the same network!" but that's easier said than done:
abstraction = [out.X] pipe(abstraction, out.X)
Might these issues be mitigated by enabling hierarchical naming for branches?
Maybe something like
pipe(out.B([out.X]), out.X) -> Namespace(X=<main out>, B=Namespace(X=<branch out>)
This might form part of a solution to #17.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently we have
which is great, but then
which is not so good.
You might say "so don't use the same output name twice in the same network!" but that's easier said than done:
Might these issues be mitigated by enabling hierarchical naming for branches?
Maybe something like
This might form part of a solution to #17.
The text was updated successfully, but these errors were encountered: