Xiu-zhe (Roger) Luo

This needs more changes since I wasn't expecting the cases with multiple entries - they make no difference with single-entry multiple sub-commands for Julia and perhaps worse latency then you...

Yes, that should do the job, and the build module indeed needs some love... I must admit that I wasn't very serious enough to rewrite this module last time.

fixed in 5af139a23262a92af7a05fc6e0333f49aa20f1af

reopen since this behaviour is not tested

yeah the documentation needs some love. you need to create a CLI project https://comonicon.org/dev/project/#Enable-System-Image then call the `YouPackage.comonicon_install()` as a CLI app.

> IonCLI is archived and ion doesn' t have a template for comonicon? not yet, I don't currently have time to work on that. You can just create a `Comonicon.toml`...

So perhaps in our new rewrite, we should consider removing this operator completely? But it would less convenient (basically meaning needs to write another layer of the match in practice)...

True, I think we still need a distinguish of local/global scope just because this is not available inside a Julia macro, but if somehow we can get macro caller scope,...

I think we should just use `$`, the meaning of this is actually clear outside quotes, e.g ```julia function Tree.print_node(io::IO, node::SpatialModulationType) @match node begin $SpatialModulationType.Global => print(io, "Global") $SpatialModulationType.ScaledLocations(_) =>...

This requires one to write ```julia @match 1 begin &Foo.Bar => true end ``` to trigger the evaluation of `Foo`, but I think `Foo.Bar` has no ambiguity here, and should...