By making Pattern et al private, you limit the utility of this system considerably. about egison-ruby

[egisatoshi]

Thanks for your comment!
Actually, I've considered about that when I've designed this library.
But I got rid of them to make this library easy to understand for many people.

By the way, you can define your own matchers as Multiset and Set, though you cannot define your own patterns for now.

[egisatoshi]

The Egison programming language that I've designed without compromise provides users all power.

[MrJoy]

I am aware of the Egison language, but using a language other than Ruby is undesirable for this specific project (as the project revolves around analysis and transformation of a Ruby token stream, it is preferable to use the native Ruby parser to ensure the highest level of accuracy in implementing Ruby's lexical rules).

Simply making Pattern non-private would enable others to extend the Egison library without adding complexity for users who do not actively seek it out.

Custom matchers are of little or no use to me without custom patterns.

[egisatoshi]

Thank you for your reply?

Are you saying you'd like to add new patterns other than element patterns and subcollection patterns?