take

Hi @ding-young are you still planning to work on this issue?

@comphead Yes, I've taken a brief look at scalar_doc_sections and the user_doc macro, and I plan to make the necessary code changes this weekend. If you need this change earlier, please tell me.

@comphead if the doc_section is a string, user_doc macro syntax will change for all functions?

Before

#[user_doc(
    doc_section(label = "String Functions"),
    description = "...",
    syntax_example = "...",
    ...
)]

After

#[user_doc(
    doc_section = "String Functions",
    description = "...",
    syntax_example = "...",
    ...
)]

I think we can make the parser to try both,
(1) try to find all these attributes

#[user_doc(
    doc_section(include=true, label = "String Functions", description: None),
    description = "...",
    syntax_example = "...",
    ...
)]

(2) if it fails look for single string like doc_section = "String Functions"

#[user_doc(
    doc_section = "String Functions",
    description = "...",
    syntax_example = "...",
    ...
)]

Thereby we can keep original syntax.
However, I'm curious whether we should replace (1) with (2), or make parser try both.

I think folks lets keep it just

doc_section(label = "String Functions"),

where label corresponds to label in predefined doc sections
in this case we avoid massive changes for all builtin functions again.

I understand that we slightly overcomplicate the doc section so it looks like a complex object but in fact it is just a string but if we want to improve it we can do it later

Agree, thanks @comphead @ding-young