On moving forward with the project

[ZILtoid1991]

I've decided to take up the task of finishing the library and getting it into a more usable state.

However, to make the task more reasonable and achieveable, I have to both drop some functions (such as the allocators and the custom error handling) and merge the optional validation into the parsing phase.

I see some potential in this library, and now I posess both the skills and time to fix it, however my visions for an XML library might not be the same as many others, especially of those in control of the Phobos library. My question is that should I just create my own dub library with my improved code, or try to submit it to Phobos inclusion despite the library no longer having an @nogc option?

[burner]

Awesome

I have to both drop some functions (such as the allocators and the custom error handling) and merge the optional validation into the parsing phase.

Even more awesome.

I would suggest to put your code into a dub package on code.dlang.org and then push for phobos inclusion.

I think nogc for a parser that builds a try is a bad idea.
If I had the time, I would remove all the allocator code and try to make it @safe and very simple to use.

Thank you for taking this one. Please inform us how it goes.