-
Notifications
You must be signed in to change notification settings - Fork 145
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
Spelling #990
base: master
Are you sure you want to change the base?
Spelling #990
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checkpointing
@@ -150,7 +150,7 @@ ns_module = mkHoleModule . ns_mod_name | |||
-- | Substitution on @{A.T}@. We enforce the invariant that the | |||
-- 'nameModule' of keys of this map have 'moduleUnitId' @hole@ | |||
-- (meaning that if we have a hole substitution, the keys of the map | |||
-- are never affected.) Alternately, this is ismorphic to | |||
-- are never affected.) Alternately, this is isomorphic to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most corrections were automatically suggested by Google Sheets. This is amongst them. In general, I don't fight Google except when I have sufficient experience to know it's wrong.
@@ -789,7 +789,7 @@ dataConUnivTyVars = dcUnivTyVars | |||
dataConExTyVars :: DataCon -> [TyVar] | |||
dataConExTyVars = dcExTyVars | |||
|
|||
-- | Both the universal and existentiatial type variables of the constructor | |||
-- | Both the universal and existential type variables of the constructor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this. Google suggested existentialism
but that didn't seem right...
@@ -1686,8 +1686,8 @@ a demand on the Id into a DmdType, which gives | |||
c) an indication of the result of applying | |||
the Id to its arguments | |||
|
|||
However, in fact we store in the Id an extremely emascuated demand | |||
transfomer, namely | |||
However, in fact we store in the Id an extremely emasculated demand |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
-- These are are implied by their type or class decl; | ||
-- These are implied by their type or class decl; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doubled words are usually typos and my tooling flags them and I try to correct them by hand. There are certain cases where the algorithm is wrong. Generally that that
is acceptable/intended. Here, I don't think the doubling is intended, and hence I've removed it.
When we initally build an Integer literal, notably when | ||
deserialising it from an interface file (see the Binary instance | ||
When we initially build an Integer literal, notably when | ||
deserializing it from an interface file (see the Binary instance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Google suggested this. Generally I leave -ise
British variants alone. But the Internet agrees that this -z
/-s
variation doesn't exist.
@@ -822,15 +822,15 @@ Similarly, consider | |||
and suppose that there are auto-generated specialisations and a strictness | |||
wrapper for g. The specialisations get activation AlwaysActive, and the | |||
strictness wrapper get activation (ActiveAfter 0). So the strictness | |||
wrepper fails the test and won't be inlined into f's stable unfolding. That | |||
wrapper fails the test and won't be inlined into f's stable unfolding. That |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably (esp. since the spelling varies in this file).
@@ -1155,7 +1155,7 @@ postInlineUnconditionally dflags env top_lvl bndr occ_info rhs unfolding | |||
-- case v of | |||
-- True -> case x of ... | |||
-- False -> case x of ... | |||
-- This is very important in practice; e.g. wheel-seive1 doubles | |||
-- This is very important in practice; e.g. wheel-sieve1 doubles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -1129,7 +1129,7 @@ The DeriveAnyClass extension adds a third way to derive instances, based on | |||
empty instance declarations. | |||
|
|||
The canonical use case is in combination with GHC.Generics and default method | |||
signatures. These allow us have have instance declarations be empty, but still | |||
signatures. These allow us to have instance declarations be empty, but still |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is one of those cases where I manually adjusted...
@@ -411,7 +411,7 @@ flatten | |||
|
|||
|
|||
---------------------------- | |||
indexed-types/should_failt/T4179 | |||
indexed-types/should_fail/T4179 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -753,7 +753,7 @@ isReturnTyVar tv | |||
|
|||
-- isAmbiguousTyVar is used only when reporting type errors | |||
-- It picks out variables that are unbound, namely meta | |||
-- type variables and the RuntimUnk variables created by | |||
-- type variables and the RuntimeUnk variables created by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -340,7 +340,7 @@ enclosing class or instance. Consider | |||
type F Int [z] = ... -- Second param must be [z] | |||
|
|||
In the CoAxBranch in the instance decl (F Int [z]) we use the | |||
same 'z', so that it's easy to check that that type is the same | |||
same 'z', so that it's easy to check that the type is the same |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I spent quite a bit of time on this one. I'm not confident about it, but...
@@ -380,7 +380,7 @@ as ATyCon. You can tell the difference, and get to the class, with | |||
The Class and its associated TyCon have the same Name. | |||
-} | |||
|
|||
-- | A typecheckable-thing, essentially anything that has a name | |||
-- | A typechecked-thing, essentially anything that has a name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably wrong
platformUnregisterised :: Bool, | ||
platformUnregistered :: Bool, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious about this term. Again, not confident (betting it'll be rejected). If the change is ok, then I'd adjust the indentation.
If the package `eta-spark-core` with the exact same version as in the commit specified can be found in Hacakge or Etlas Index, the GitHub location will override the other search locations. This makes it easy to depend on forked versions of existing libraries when the released versions of those libraries don't contain the functionality required for your project. | ||
If the package `eta-spark-core` with the exact same version as in the commit specified can be found in Hackage or Etlas Index, the GitHub location will override the other search locations. This makes it easy to depend on forked versions of existing libraries when the released versions of those libraries don't contain the functionality required for your project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -14,7 +14,7 @@ | |||
-- | | |||
-- Module : GHC.Float | |||
-- Copyright : (c) The University of Glasgow 1994-2002 | |||
-- Portions obtained from hbc (c) Lennart Augusstson | |||
-- Portions obtained from hbc (c) Lennart Augustsson |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Name...
-- To and from from ST | ||
-- To and from ST |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -676,7 +676,7 @@ mkDuplexHandle dev filepath mb_codec tr_newlines = do | |||
mkHandle dev filepath WriteHandle Nothing mb_codec | |||
tr_newlines | |||
(Just handleFinalizer) | |||
Nothing -- no othersie | |||
Nothing -- no otherside |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly otherwise
, but given there are sides a few lines below...
@@ -86,7 +86,7 @@ last [] = errorEmptyList "last" | |||
#else | |||
-- Use foldl to make last a good consumer. | |||
-- This will compile to good code for the actual GHC.List.last. | |||
-- (At least as long it is eta-expaned, otherwise it does not, #10260.) | |||
-- (At least as long it is eta-expand, otherwise it does not, #10260.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
possibly expanded
?
@@ -386,7 +386,7 @@ public static StgContext acquire() { | |||
public final void dump() { | |||
System.out.println("Context Dump"); | |||
System.out.println("currentTSO: " + currentTSO); | |||
System.out.println("myCapabilitymyCapability: " + myCapability); | |||
System.out.println("myCapability: " + myCapability); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Description
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at jsoref@5a440c4#commitcomment-79875390
How Has This Been Tested?
The action reports that the changes in this PR would make it happy: jsoref@28d74f3
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Types of changes
It's quite possible there are breaking changes. I fully expect this will need to be split or something. I'm very comfortable w/ working on large changesets. I just need direction about how each project prefers to address them.
Checklist: