New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime vs run-time #167
Comments
Which one do you prefer? |
Run-time is antiquated. Let's consistently use runtime for all uses. (But I question whether these uses are really appropriate, because they suggest a separation between translation and execution that is not required...) |
FWIW - I just want to second richard's questioning of the separation between translation and execution - since I remember a thread during which several of the core folks argued viguorously that the standard maintains no distinction between compile-time and run-time execution (at the expense of clarity in specifying the real connotations behind constant expressions in my opinion - but I have sympathy for their arguments) |
@faisalv: This is an editorial issue to harmonize the spelling of "runtime". This has been addressed. I think any questions about talking about "runtime" in the first place should be directed to CWG or LWG with specific examples. |
@jensmaurer thanks - i'm aware this is an editorial issue - just cared enough to document seconding Richard's raising the question on this thread - will leave it to those who argued so ardently against the distinction to approach the WGs. |
is there a good reason for using both spellings in the standard? might be nicer to stick to one ...
The text was updated successfully, but these errors were encountered: