down the server. See https://github.com/Pylons/waitress/pull/399 Fixed testing of vendored asyncore code to not rely on particular naming for errno's. See https://github.com/Pylons/waitress/pull/397 HTTP accidentally treat non-printable characters as whitespace and lead to a potental HTTP request smuggling/splitting security issue. Thanks to ZeddYu Lu for the extra test cases. Please see the security advisory front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting. Please see the security advisory for more information: https://github.com/Pylons/waitress/sec

accidentally treat non-printable characters as whitespace and lead to a potental HTTP request smuggling/splitting security issue. Thanks to ZeddYu Lu for the extra test cases. Please see the security advisory front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting. Please see the security advisory for more information: https://github.com/Pylons/waitress/sec same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message

accidentally treat non-printable characters as whitespace and lead to a potental HTTP request smuggling/splitting security issue. Thanks to ZeddYu Lu for the extra test cases. Please see the security advisory front-end server to treat a request different from Waitress. This could lead to HTTP request smuggling/splitting. Please see the security advisory for more information: https://github.com/Pylons/waitress/sec same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message

hGetContents: invalid argument (invalid byte sequence) If this happens, you can try changing the console code page [https://docs.microsoft.com/en- us/windows-server/administration/windows-commands/chcp] to UTF-8 in Emacs and load it by pressing C-c C-l (Ctrl+c followed by Ctrl+l). You should now see that the code is highlighted and there should be a message *All done*. If this is the case, congratulations! You {-# COMPILE GHC putStrLn = putStrLn . T.unpack #-} main : IO ⊤ main = putStrLn "Hello world!" This code is self-contained and has several declarations: 1. Imports of the ÌO, ⊤ and String types from the

hGetContents: invalid argument (invalid byte sequence) If this happens, you can try changing the console code page [https://docs.microsoft.com/en- us/windows-server/administration/windows-commands/chcp] to UTF-8 in Emacs and load it by pressing C-c C-l (Ctrl+c followed by Ctrl+l). You should now see that the code is highlighted and there should be a message *All done*. If this is the case, congratulations! You {-# COMPILE GHC putStrLn = putStrLn . T.unpack #-} main : IO ⊤ main = putStrLn "Hello world!" This code is self-contained and has several declarations: 1. Imports of the ÌO, ⊤ and String types from the

hGetContents: invalid argument (invalid byte sequence) If this happens, you can try changing the console code page [https://docs.microsoft.com/en- us/windows-server/administration/windows-commands/chcp] to UTF-8 in Emacs and load it by pressing C-c C-l (Ctrl+c followed by Ctrl+l). You should now see that the code is highlighted and there should be a message *All done*. If this is the case, congratulations! You {-# COMPILE GHC putStrLn = putStrLn . T.unpack #-} main : IO ⊤ main = putStrLn "Hello world!" This code is self-contained and has several declarations: 1. Imports of the ÌO, ⊤ and String types from the

hGetContents: invalid argument (invalid byte sequence) If this happens, you can try changing the console code page [https://docs.microsoft.com/en- us/windows-server/administration/windows-commands/chcp] to UTF-8 in Emacs and load it by pressing C-c C-l (Ctrl+c followed by Ctrl+l). You should now see that the code is highlighted and there should be a message *All done*. If this is the case, congratulations! You {-# COMPILE GHC putStrLn = putStrLn . T.unpack #-} main : IO ⊤ main = putStrLn "Hello world!" This code is self-contained and has several declarations: 1. Imports of the ÌO, ⊤ and String types from the

Anonymous modules Basics Private definitions Name modifiers Re-exporting names Parameterised modules Splitting a program over multiple files Datatype modules and record modules Mutual Recursion Old Syntax refl test₂ : backward-2 enum-Nat 5 ≡ 3 test₂ = refl Note that if we want to use automated case-splitting and pattern matching to implement one of the fields, we need to do so in a separate definition. The FOREIGN pragma The GHC backend interprets FOREIGN pragmas as inline Haskell code and can contain arbitrary code (including import statements) that will be added to the compiled module. For instance:

Getting Started Prerequisites Installation Quick Guide to Editing, Type Checking and Compiling Agda Code Language Reference Abstract definitions Built-ins Coinduction Copatterns Core language Data Types Installation Flags Quick Guide to Editing, Type Checking and Compiling Agda Code Introduction Menus Writing mathematical symbols in source code Errors Compiling Agda programs Batch-mode command Prerequisites triggers an error message. Default: off. Quick Guide to Editing, Type Checking and Compiling Agda Code Introduction Agda programs are commonly edited using Emacs [http://www.gnu.org/software/emacs/]

Getting Started Prerequisites Installation Quick Guide to Editing, Type Checking and Compiling Agda Code Language Reference Abstract definitions Built-ins Coinduction Copatterns Core language Data Types Installation Flags Quick Guide to Editing, Type Checking and Compiling Agda Code Introduction Menus Writing mathematical symbols in source code Errors Compiling Agda programs Batch-mode command Prerequisites triggers an error message. Default: off. Quick Guide to Editing, Type Checking and Compiling Agda Code Introduction Agda programs are commonly edited using Emacs [http://www.gnu.org/software/emacs/]