|
|
CONVERSION ERROR
|
|
|
# Areas We'd Like To See Covered In More Depth
|
|
|
|
|
|
Error: HttpError (HttpExceptionRequest Request {
|
|
|
host = "ghc.haskell.org"
|
|
|
port = 443
|
|
|
secure = True
|
|
|
requestHeaders = []
|
|
|
path = "/trac/ghc/wiki/MoreDepth"
|
|
|
queryString = "?version=8"
|
|
|
method = "GET"
|
|
|
proxy = Nothing
|
|
|
rawBody = False
|
|
|
redirectCount = 10
|
|
|
responseTimeout = ResponseTimeoutDefault
|
|
|
requestVersion = HTTP/1.1
|
|
|
}
|
|
|
(StatusCodeException (Response {responseStatus = Status {statusCode = 403, statusMessage = "Forbidden"}, responseVersion = HTTP/1.1, responseHeaders = [("Date","Sun, 10 Mar 2019 06:56:22 GMT"),("Server","Apache/2.2.22 (Debian)"),("Strict-Transport-Security","max-age=63072000; includeSubDomains"),("Vary","Accept-Encoding"),("Content-Encoding","gzip"),("Content-Length","249"),("Content-Type","text/html; charset=iso-8859-1")], responseBody = (), responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose}) "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>403 Forbidden</title>\n</head><body>\n<h1>Forbidden</h1>\n<p>You don't have permission to access /trac/ghc/wiki/MoreDepth\non this server.</p>\n<hr>\n<address>Apache/2.2.22 (Debian) Server at ghc.haskell.org Port 443</address>\n</body></html>\n"))
|
|
|
- The build system (for example)
|
|
|
- It would be quite interesting to hear what parts of GHC are changing rapidly and what parts seem quite stable. Also, into which corners of the compiler do the righteous fear to tread? (The evil mangler?)
|
|
|
- It is unclear how binding group analysis influences the use of 1 abstract syntax (HsSyn): how is the required ordering and grouping implemented, how does it affect error messages?
|
|
|
- How does this Cabal thing work?
|
|
|
- How to read a dailysnapshot build log.
|
|
|
- Does ghc compile with VisualHaskell yet?
|
|
|
- In the compiler pipeline, please explain a little more about the invariants as a program flows through the pipeline. For example, toward the back end, it would be useful to know at what point the following become known:
|
|
|
|
|
|
Original source:
|
|
|
|
|
|
```trac
|
|
|
= Areas We'd Like To See Covered In More Depth =
|
|
|
|
|
|
|
|
|
* The build system (for example)
|
|
|
* It would be quite interesting to hear what parts of GHC are changing rapidly and what parts seem quite stable. Also, into which corners of the compiler do the righteous fear to tread? (The evil mangler?)
|
|
|
* It is unclear how binding group analysis influences the use of 1 abstract syntax (HsSyn): how is the required ordering and grouping implemented, how does it affect error messages?
|
|
|
* How does this Cabal thing work?
|
|
|
* How to read a dailysnapshot build log.
|
|
|
* Does ghc compile with VisualHaskell yet?
|
|
|
* In the compiler pipeline, please explain a little more about the invariants as a program flows through the pipeline. For example, toward the back end, it would be useful to know at what point the following become known:
|
|
|
* layout of heap objects
|
|
|
* explicit heap pointer (allocation pointer)
|
|
|
* explicit stack pointer
|
|
|
``` |
|
|
- layout of heap objects
|
|
|
- explicit heap pointer (allocation pointer)
|
|
|
- explicit stack pointer
|
|
|
- What optimizations happen in the simplifier? How do they work? |