MichaelHatherly/Docile.jl

is there a way we could generate docs for generated code as in the above link

The combination of @eval and string interpolation is probably raising a
UndefVarError: op not defined error, yes? I've not had much success resolving
that and it appears to still be a problem with Base.@doc as well.

You can pull the interpolation outside of the @doc with something like:

for op in [:a, :b, :c]
    text = "$(op)"
    @eval begin
        @doc $(text) ->
        $(op)(x) = x
    end
end

which should work with Docile.@doc and Base.@doc.

Personally, what I've found is that documenting using loops tends to lead to repetitive
docs where things might be better split up into a single doc for the general case and
several other docs for the specific cases.

In the context of QuODESolvers and their subtypes perhaps adding a general docstring
to QuODESolvers and then anything more specific to each subtype op in the loop.

@doc """
...
""" ->
abstract QuODESolvers <: QuPropagatorMethod

const type_to_method = @compat Dict{Any, Any}(#...

const subtypedocs = @compat Dict(#...

for op in keys(type_to_method)
    text = subtypedocs[op]
    @eval  begin
        @doc $(text) ->
        immutable $op <: QuODESolvers
            options::Dict{Symbol, Any}
        end
        $op() = $op(Dict())
    end
end

where subtypedocs is a Dict containing the docstrings specific to each subtype.

I've only skimmed over the package though, so that might go against how you'd like to
organise things.