Add the ability to define terms that are never word-broken

[DarkArc]

Is your feature request related to a problem? Please describe.

The problem is in documenting C++ code, what sometimes happens is you encounter something like:

/*some long text */ in C+
+ do this:

It would be nice if C++ did not wrap on the individual + characters, e.g.:

/*some long text */ in
C++ do this:

See also:
https://superuser.com/questions/1841412/preventing-word-break-in-markdown-and-rst

Describe the solution you'd like
I think the ideal is to add a set in the configuration of "project terms" both for searching purposes and line wrap purposes, so that Sphinx would understand these special technical words that contain symbols (that should not be wrapped).

Describe alternatives you've considered

A "don't break words" setting could also work. Presumably there's a reason why this is not done though.

[kaycebasques]

This occurs within normal reST text, is that right? E.g. a normal paragraph containing the text C++ might put the break between the two + characters.

[DarkArc]

Forgive my lack of knowledge about the project structure; but I'd assume reStructuredText is just the markup specification and maybe parser. The decision to word break or not is ultimately down to the format that is produced (which seems squarely in Sphinx's ballpark).

[kaycebasques]

Yes, it sounds like a markup-agnostic problem that needs to be handled at the Sphinx level. To rephrase my original question: can you provide an example that reproduces the problem?