Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

An idea: Introduce quoting as a expression/data transformation from the beginning #9

Closed
wants to merge 2 commits into from

Conversation

MilesMcBain
Copy link

@MilesMcBain MilesMcBain commented Sep 6, 2018

I applaud the big push being made here!

I have some feedback and a suggestion on how to explain quoting.

This text is the type of thing I found befuddling early on when I was trying to understand quoting:

On the other hand, a quoting function is not passed the value of an expression, it is passed the expression itself. We say the argument has been automatically quoted. The quoted expression might be evaluated a bit later or might not be evaluated at all. The simplest quoting function is quote(). It automatically quotes its argument and returns the quoted expression without any evaluation.

I think 'we say the argument has been automatically quoted' seems a bit detached from any kind of mechanism I can map to. Perhaps I am just a dense concrete thinker, but I really got quoting as soon as I understood it in terms of a transformation from code (expressions) to data. This PR contains some changes to surface that theme.

I relinquish all my rights to the work contained in this PR to RStudio.

- add class calls to expose the different types of data and highlight
differences.

- Change description of "" operator to continue data vs expression theme.
@lionel-
Copy link
Member

lionel- commented Sep 6, 2018

Can you move this to an issue please? Changing the strategy of how we teach tidy eval requires a discussion.

@MilesMcBain
Copy link
Author

Okay done!

@MilesMcBain MilesMcBain closed this Sep 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants