Misspelled COMANND

[weaversa]

cryptol/cry

Line 14 in eeadea1

Usage: $0 COMMAND COMANND_OPTIONS

[brianhuffman]

I've actually been meaning to make a ticket thread to keep track of all the typos I find in the Cryptol repo, so I can batch the fixes together (it never seems worth the trouble to make a PR just to fix one typo). Here are some others that I know of:

• cryptol/src/Cryptol/TypeCheck/Type.hs

  Line 116 in eeadea1

  -- The last field gives us some infor for nicer warnings/errors.

• cryptol/src/Cryptol/TypeCheck/Error.hs

  Line 45 in eeadea1

  dropSumbsumed survived xs =

• cryptol/src/Cryptol/TypeCheck/Monad.hs

  Line 116 in eeadea1

  do coutner <- newIORef 0

• cryptol/src/Cryptol/TypeCheck/Infer.hs

  Line 655 in eeadea1

  -- as monomorphic, then we don't do generalzation.

• cryptol/src/Cryptol/ModuleSystem/Name.hs

  Line 175 in eeadea1

  -- the need for parenthesis.

• cryptol/src/Cryptol/TypeCheck/Error.hs

  Line 132 in eeadea1

  -- ones with the has highest rating accorign to this function

• cryptol/cry

  Line 14 in eeadea1

  Usage: $0 COMMAND COMANND_OPTIONS

• cryptol/src/Cryptol/Eval.hs

  Line 330 in eeadea1

  -- be implemented rather more efficently than general types because we can

[yav]

I am proud to say that I probably made most of these :)
Why not just fix them in the code as you find them?

[brianhuffman]

Because I'm usually in the middle of making a PR for something unrelated when I find them.

Actually, I'd guess that the "efficently" is Rob's; he's made that typo before in crucible and so I did git grep efficent just now and found it

[brianhuffman]

I just made a PR for all of those. Updating an issue thread is probably too much work to do in the future, so instead I'll just note typos locally when I find them and make PRs whenever it seems reasonable.