I see, but isn't that true for any library? xD
In the end, `Parsed` should only be handled whereever you receive the initial input, so the rest of your business logic will be free of it :)
In the end, this is just a tool and it's fine if it isn't fitting your particular style or use case ;)
Yes, there's nothing particularly wrong with it, but core types should be standardized or you end up with multiple string libraries (as in C) or multiple dependency injection libraries (as in Java). Validation libraries already exist for Java.
So if this sort of thing takes off there is likely to be a standardization process at some point.
Go works better for this because common interfaces can be implemented by "coincidence." (Structural types.)
The advantage is that you can write code using generics that works with any parser, but I'm a little skeptical about the value of generic code.
[1] https://github.com/parsix/parsix#build-your-own-parse