#getmethod that returns the related
Callableinstance that you could then directly invoke
A macro generates code only in the location in which it is executed.
However.....you can make what you want to do work with macros.
Macros have access to constants.
So, if you generate all of your procs, assigned to a constant name, under a common namespace, then in your main.cr you can iterate over
that namespace (see Crystal::Maros::TypeNode in the Crystal API docs), find the names of all of your Proc constants, and build your master hash.
#registermethod then too
macro some_nameare reusable portions of macro code, but you can also use the macro code outside of them