[Git][ghc/ghc][master] Avoid utf8 in primops.txt.pp comments

[Marge Bot (@marge-bot)]

Marge Bot pushed to branch master at Glasgow Haskell Compiler / GHC


Commits:
0325a6e5 by Greg Steuck at 2024-01-24T01:29:44-05:00
Avoid utf8 in primops.txt.pp comments

They don't make it through readFile' without explicitly setting the
encoding. See https://gitlab.haskell.org/ghc/ghc/-/issues/17755

- - - - -


1 changed file:

- compiler/GHC/Builtin/primops.txt.pp


Changes:

=====================================
compiler/GHC/Builtin/primops.txt.pp
=====================================
@@ -2882,9 +2882,9 @@ section "Continuations"
     'control0#' will fail by raising an exception. However, such violations
     are only detected on a best-effort basis, as the bookkeeping necessary for
     detecting /all/ illegal uses of 'control0#' would have significant overhead.
-    Therefore, although the operations are “safe” from the runtime’s point of
+    Therefore, although the operations are "safe" from the runtime's point of
     view (e.g. they will not compromise memory safety or clobber internal runtime
-    state), it is still ultimately the programmer’s responsibility to ensure
+    state), it is still ultimately the programmer's responsibility to ensure
     these invariants hold to guarantee predictable program behavior.
 
     In a similar vein, since each captured continuation includes the full local
@@ -2896,13 +2896,13 @@ section "Continuations"
     finish reading it when it is resumed; further attempts to resume from the
     same place would then fail because the file handle was already closed.
 
-    In other words, although the RTS ensures that a computation’s control state
+    In other words, although the RTS ensures that a computation's control state
     and local variables are properly restored for each distinct resumption of
     a continuation, it makes no attempt to duplicate any local state the
     computation may have been using (and could not possibly do so in general).
     Furthermore, it provides no mechanism for an arbitrary computation to
     protect itself against unwanted reentrancy (i.e. there is no analogue to
-    Scheme’s @dynamic-wind@). For those reasons, manipulating the continuation
+    Scheme's @dynamic-wind@). For those reasons, manipulating the continuation
     is only safe if the caller can be certain that doing so will not violate any
     expectations or invariants of the enclosing computation. }
 ------------------------------------------------------------------------



View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/commit/0325a6e54977363da457e349805c101ca2d90a1f

-- 
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/commit/0325a6e54977363da457e349805c101ca2d90a1f
You're receiving this email because of your account on gitlab.haskell.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-commits/attachments/20240124/59a2f963/attachment-0001.html>