Allow "!" and "\" in wire naming

[myles-fb]

I receive an error saying "Invalid name" if I try to name a wire with either of those characters

[bsiever]

Thanks --- I'll consider it. A common convention is use of lower case n to indicate negation. Like "nA" for "not A" (I tend to use camelCase when doing this). You might consider this approach until I can review the issue.

[AmityWilder]

If relaxed wire names are elected to be the correct behavior, #21 is all that would be required to implement it.

Considerations

Removing the naming restriction from wires doesn't affect circuit creation, saving, or loading¹. However, it is important to note that named wires can be watched.

It's possible that lifting this restriction on wire names would mean wires have no guarantee of being valid Java variable names. I'm not sure if that affects DLUnit tests; if it does, that could be catastrophic if not handled.

Solutions

If watchable elements do not need to be Java-variable-name-compatible, there is no issue.

If they do, watched wires could have their names sanitized² behind the scenes specifically for the purposes of DLUnit.
This sanitized ID could be displayed as a tooltip if users need to use them for writing custom unit tests.

Footnotes

1. This is pointed out because circuit names, unlike named wires, do affect saving/loading due to the typical restrictions of the filesystem. ↩

2. And pre/appended with a unique code in case of name collisions like X\{a,b} → X__a_b_ with X!(a+b) → X__a_b_. ↩