Skip to content
New issue

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

Explore using object references instead of object.name #100

Open
ashutshkumr opened this issue Aug 27, 2021 · 0 comments
Open

Explore using object references instead of object.name #100

ashutshkumr opened this issue Aug 27, 2021 · 0 comments
Assignees

Comments

@ashutshkumr
Copy link
Contributor

ashutshkumr commented Aug 27, 2021

Based on feedback from multiple users, second approach is generally perferred.

p1, p2, p3 = config.ports.port().port().port()

f1, f2 = config.flows.flow().flow()

f1.tx_rx.port.tx_name = p1.name
f1.tx_rx.port.rx_name = p2.name

f2.tx_rx.port.tx_name = p1.name
f2.tx_rx.port.rx_name = p3.name
p1, p2, p3 = config.ports.port().port().port()

f1, f2 = config.flows.flow().flow()

f1.tx_rx.port.tx_name = p1
f1.tx_rx.port.rx_name = p2

f2.tx_rx.port.tx_name = p1
f2.tx_rx.port.rx_name = p3

This requires working out following:

  • is it feasible in Go and Python
  • how will the impl work during serdes

More details to be discussed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants