Use procedural macro for g!
and s!
macros
#170
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This gives us much more expressivity in the macros:
{..}
when you need to call methods or access tuple or array elements..*
dot product operator which replaces manually calledop::lincomb
./
(mostly for fun -- it's used in one place in ecdsa_fun).RIP macro_rules stack machine.
In order to design the thing correctly I also tried to make everything copy (#146) to maintain backwards compat with omitting &.
In the end I didn't really use that but instead just allowed you to pass a reference to most of the functions in op which also fixes #125.
This is probably a breaking change due to some slight changes in the way some parts of the expressions are interpreted.
I've done benchmarks to confirm that there's no performance regression in terms of what is produced.
Fixes #146 #125 #6