Documentation Should use "Real"

[friedmud]

Reason

Documentation for objects should use "Real" instead of "double".

For example, look at the "default" parameter here: https://mooseframework.org/source/postprocessors/Receiver.html

Design

See above

Impact

More accurate: the documentation should reflect what people need to type in code.

[jmeziere]

@friedmud These changes would need to be made in the .md files, correct? Also, these are all over the place, correct? We'd need to use a finder, and go through all the instances of double that show up and decide if it is supposed to be there or not?

[JackHanni]

@permcody @friedmud These changes would need to be made in the .md files, correct? Also, these are all over the place, correct? We'd need to use a finder, and go through all the instances of double that show up and decide if it is supposed to be there or not?

[permcody]

Hi Jack, Actually no, the tables you see on the documentation page aren't built from explicit markup in the .md files. They are generated automatically from the dump of syntax from the inputParameters functions that are spread throughout MOOSE. The issue is that Real is just a typedef for double so we are losing the "alias" somewhere along the way. This should actually be a really small change but will require a fair amount of sleuthing. I don't know if the Real type is getting lost in the dump (on the C++ side) or in the table generation on the Python side. Tagging @aeslaughter to see if he knows.

What this ticket is not is changing a bunch of files all over the place, it's hopefully just one or two small changes. It's still important though. Thanks for your interest.