Add yard-tomdoc

[jacobbednarz]

This adds the ability for developers to document their code using tomdoc
instead of the YARD format and have the generated output respect those
directives.

Fixes #62

[jacobbednarz]

@lsegal any thoughts on this one?

[lsegal]

As it stands, the plugin globally rewrites the default docstring parser across the entire YARD process, which means that it would potentially cause problems in rubydoc's current architecture. It's not safe to merge this in as is, unfortunately.

There isn't really a good general API to segregate the use of docstring parsers across runs of YARD.parse. Although yard-tomdoc works great in a single process or for a single project, it doesn't really work well in this specific context.

We would probably have to do some architecture work on rubydoc.info, stuff that is, arguably, long overdue, before we can handle a plugin like this on the site. @zapnap and I have been discussing reworking the site to use worker queues, possibly through docker, which would have plenty of other benefits in addition to the process segregation aspect. The problem, though, ultimately comes to the part where we are serving HTML via the renderer, and that's a slightly harder problem to solve (worker queues won't help there).

[jacobbednarz]

no worries! closing this one off and will look at another option.