Skip to content
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

Awkward sentence #2

Open
leonidr-da opened this issue May 3, 2020 · 0 comments
Open

Awkward sentence #2

leonidr-da opened this issue May 3, 2020 · 0 comments

Comments

@leonidr-da
Copy link
Contributor

I think that "These concepts are represented first class in the language." is a bit awkward, and a little bit misleading.

First, to quibble with the "first class" usage; the authorization/privacy of a contract isn't something that we can pass around within a language, like we can parameters. This has been my understanding of the term. For example it isn't something that a choice can create. Rather it is something that we specify. Second, and moot if you accept my first quibble, "first class" is an adjective on its own and "represented" is superfluous.

Altogether though, I would replace the sentence with something like:
"These concepts have a natural representation and usage pattern."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant