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
[It would be useful to add] some debugging specific features to conduit. Like a totalview extension that when compiled in gives some extra details in the "dive" menu of totalview so that digging into the conduit nodes is more easily decipherable?
For example, the current dive on a conduit node is pretty intimidating to look at and does not give the data in the same way you code to it or see it in the to_string print outs.
If you added the totalview functions to register an additional view of the data you could add some strings to just express the node as it looks to the user on a print out. Or give the current nodes string name that is used to access it as a easily seen item. Just as an example.
The text was updated successfully, but these errors were encountered:
From a developer, Ryan Bleile:
[It would be useful to add] some debugging specific features to conduit. Like a totalview extension that when compiled in gives some extra details in the "dive" menu of totalview so that digging into the conduit nodes is more easily decipherable?
For example, the current dive on a conduit node is pretty intimidating to look at and does not give the data in the same way you code to it or see it in the to_string print outs.
If you added the totalview functions to register an additional view of the data you could add some strings to just express the node as it looks to the user on a print out. Or give the current nodes string name that is used to access it as a easily seen item. Just as an example.
The text was updated successfully, but these errors were encountered: