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.

Sign up for GitHub

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

Jump to bottom

Normalize readonly #4

Open
mikedamay opened this issue Jun 27, 2020 · 1 comment
Open

Normalize readonly #4

mikedamay opened this issue Jun 27, 2020 · 1 comment

Comments

@mikedamay
Copy link
Contributor

mikedamay commented Jun 27, 2020 •
edited
Loading

We could normalize away readonly and const for exercises that do not have const/readonly as a prerequisite.

Is it worth the effort/possible maintenance headache?

For this sort of thing maybe it's easier to live with a few more representations?
@ErikSchierboom
Copy link
Member

Is it worth the effort/possible maintenance headache?

Good question. We could maybe make it a contextual optimization, in that we only apply it to some specific exercises. I do like the suggestion to normalize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ErikSchierboom @mikedamay