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

typecheck vs type-check vs type check #2

Open
wilbowma opened this issue Nov 20, 2020 · 1 comment
Open

typecheck vs type-check vs type check #2

wilbowma opened this issue Nov 20, 2020 · 1 comment

Comments

@wilbowma
Copy link

Was having this debate during a submission today. Do y'all have opinions?

My reasoning was to apply the same rationale as runtime vs run-time vs run time: type check when type is modifying the verb check, type-check when acting as a phrase modifying something else such as type-checking algorithm, and never typecheck.

@sampsyo
Copy link
Contributor

sampsyo commented Nov 20, 2020

Happy PLDying, @wilbowma!

Here is my feeling on this: one first has to make a judgment call about whether the verb is type-check or typecheck. I don't know the answer to this; it depends on how far down the road of language drift we are. This style guide should probably stake an opinion one way or another but we haven't yet. But after that:

  • If you chose the closed version, typecheck, it's always typecheck. Typechecking, typechecker, etc., etc.
  • If you chose the hyphenated version, then definitely type-checking algorithm, but what about this program does not type check or type-check? I guess probably the open version, but it's weirder than run time because it's a verb instead of a noun.

So I guess this answer is not much more useful than, like, 🤷‍♀️.

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

2 participants