-
Notifications
You must be signed in to change notification settings - Fork 210
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
Output in examples #456
Comments
That's a custom for lubridate. I don't think it was me who started it, I think I just followed on the style. While it's a bit tedious to maintain it's surely convenient for the user. Deleting those comments would be wasteful IMO, especially now when the API is stable. |
I think it's a bad idea because it's inconsistent with other packages, and there are definitely already differences between the output and the comment. Good writing/coding involves being willing to delete stuff that no longer works. |
When viewed online or in a pdf printout this inline output is definitely useful. Many people are still printing doc pages (I see it all the time with my students). I personally wouldn't care as I can execute and edit code directly form the help page in ESS. In other editors you cannot do that and people have to peruse the help page or have to run In any case, if you feel strongly about it then let's remove them. It would save me some time in the future. Manually pasting output is not the most pleasant activity. |
I have some free time I'll have a go at removing it. It's not very high priority, but I think it's worthwhile. |
e.g. in
coercion.r
, why do we have the output pasted into the examples?This seems like an easy way to end up with code and results out of sync.
The text was updated successfully, but these errors were encountered: