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

[FEA]: edge's should have an ident string #401

Open
2 tasks done
dagardner-nv opened this issue Sep 27, 2023 · 0 comments
Open
2 tasks done

[FEA]: edge's should have an ident string #401

dagardner-nv opened this issue Sep 27, 2023 · 0 comments
Labels
feature request New feature or request

Comments

@dagardner-nv
Copy link
Contributor

Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Low (would be nice)

Please provide a clear description of problem this feature solves

Similar to #400, the MRC builder knows the names of both nodes the edge is connecting to and could easily construct a string like "/seg1/A <-- /seg1/B" and supply it to the edge at construction time.

This would allow for easier debugging in MRC.

Describe your ideal solution

Ideally Builder would pass in the name of both nodes to the EdgeBuilder, this way both EdgeHolders will know the name of the node they're a holder for, and the edge would know the names of both nodes.

This way all three classes can override the << operator and print some meaningful information to the console and/or would have some identifying attributes visible in the debugger.

Describe any alternatives you have considered

No response

Additional context

No response

Code of Conduct

  • I agree to follow MRC's Code of Conduct
  • I have searched the open feature requests and have found no duplicates for this feature request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: Review - Ready for Review
Development

Successfully merging a pull request may close this issue.

1 participant