IT WORKS!!!!

First version that seems to build everything without a hitch!

README.md

@@ -1,3 +1,19 @@
+# Zelm
+
+This is a conservative fork of the Elm compiler. It aims to preserve complete
+backwards compatibility and (nearly) complete forwards comptability with the
+mainline Elm compiler as of Elm 0.19.1.
+
+We say "nearly" because there are certain bugs in the Elm compiler that will be
+fixed by the Zelm compiler. In particular some code which compiles successfully
+using the Zelm compiler may cause the mainline Elm compiler to crash.
+
+Zelm's main purpose is to provide a method for bug fixes and patches 
+
+For a more in-depth look at 
+
+**The following is the README for the original Elm compiler:**
+
 # Elm
 
 A delightful language for reliable webapps.

REASONING.md

@@ -274,7 +274,6 @@ As such Zelm hopes to
 **These are hopes not commitments.** But I do consider them valid barometers of
 whether Zelm has a project has succeeded.
 
-
 Because Zelm does not intend (at least not until 2025) to do feature
 development on the Elm language itself, Zelm makes a different set of social
 trade-offs compared to Elm itself.
@@ -287,13 +286,18 @@ and no changes to any APIs.
 **Much like the technical goals, the social goals of Zelm are very tightly
 scoped to this goal of responsiveness**.
 
-I hope that by intentionally side-stepping questions of 
+To achieve this goal of timeliness, Zelm makes two trade-offs that are very
+different from Elm itself.
+
+1. We intentionally are side-stepping many fundamental design questions around
+   the language itself, at least until 2025.
+2. We intend to lead by committee rather than individual.
 
-Zelm prefers to lead by committee rather than individual.
+The first point hopefully will allow us 
 
-We hope to have a stable roster of at least five people managing `zelm` and
-`zelm-explorations`, maybe more (although for tie-breaking purposes I'd like to
-keep the number odd).
+In particular, our eventual goal is to have a stable roster of at least five
+people managing `zelm` and `zelm-explorations`, maybe more (although for
+tie-breaking purposes I'd like to keep the number odd).
 
 # FAQ
 

builder/src/Deps/Solver.hs

@@ -390,14 +390,15 @@ constraintsDecoder =
 
 
 data Env =
-  Env Stuff.PackageCache Http.Manager Connection Registry.ZelmRegistries
+  Env Stuff.PackageCache Http.Manager Connection Registry.ZelmRegistries Stuff.PackageOverridesCache
 
 
 initEnv :: IO (Either Exit.RegistryProblem Env)
 initEnv =
   do  mvar  <- newEmptyMVar
       _     <- forkIO $ putMVar mvar =<< Http.getManager
       cache <- Stuff.getPackageCache
+      packageOverridesCache <- Stuff.getPackageOverridesCache
       zelmCache <- Stuff.getZelmCache
       customRepositoriesConfigLocation <- Stuff.getOrCreateZelmCustomRepositoryConfig
       customRepositoriesDataOrErr <- loadCustomRepositoriesData customRepositoriesConfigLocation
@@ -413,7 +414,7 @@ initEnv =
                     do  eitherRegistry <- Registry.fetch manager zelmCache customRepositoriesData
                         case eitherRegistry of
                           Right latestRegistry ->
-                            return $ Right $ Env cache manager (Online manager) latestRegistry
+                            return $ Right $ Env cache manager (Online manager) latestRegistry packageOverridesCache
 
                           Left problem ->
                             return $ Left $ problem
@@ -422,10 +423,10 @@ initEnv =
                     do  eitherRegistry <- Registry.update manager zelmCache cachedRegistry
                         case eitherRegistry of
                           Right latestRegistry ->
-                            return $ Right $ Env cache manager (Online manager) latestRegistry
+                            return $ Right $ Env cache manager (Online manager) latestRegistry packageOverridesCache
 
                           Left _ ->
-                            return $ Right $ Env cache manager Offline cachedRegistry
+                            return $ Right $ Env cache manager Offline cachedRegistry packageOverridesCache
 
 
 

builder/src/File.hs

@@ -172,8 +172,11 @@ encodingError path ioErr =
 writeBuilder :: FilePath -> B.Builder -> IO ()
 writeBuilder path builder =
   IO.withBinaryFile path IO.WriteMode $ \handle ->
-    do  IO.hSetBuffering handle (IO.BlockBuffering Nothing)
+    do  print "writeBuilder 1"
+        IO.hSetBuffering handle (IO.BlockBuffering Nothing)
+        print "writeBuilder 2"
         B.hPutBuilder handle builder
+        print "writeBuilder 3"
 
 
 

builder/src/Stuff.hs

@@ -12,10 +12,13 @@ module Stuff
   , withRegistryLock
   , PackageCache
   , ZelmSpecificCache
+  , PackageOverridesCache
   , getPackageCache
   , getZelmCache
+  , getPackageOverridesCache
   , registry
   , package
+  , packageOverride
   , getReplCache
   , getElmHome
   , getOrCreateZelmCustomRepositoryConfig
@@ -163,12 +166,21 @@ newtype PackageCache = PackageCache FilePath
 
 newtype ZelmSpecificCache = ZelmSpecificCache FilePath
 
+newtype PackageOverridesCache = PackageOverridesCache FilePath
+
 
 getPackageCache :: IO PackageCache
 getPackageCache =
   PackageCache <$> getCacheDir "packages"
 
 
+getPackageOverridesCache :: IO PackageOverridesCache
+getPackageOverridesCache =
+  do
+    (ZelmSpecificCache zelmSpecificCache) <- getZelmCache
+    pure $ PackageOverridesCache zelmSpecificCache
+
+
 getZelmCache :: IO ZelmSpecificCache
 getZelmCache =
   ZelmSpecificCache <$> getOrCreateZelmCacheDir
@@ -184,6 +196,11 @@ package (PackageCache dir) name version =
   dir </> Pkg.toFilePath name </> V.toChars version
 
 
+packageOverride :: PackageOverridesCache -> Pkg.Name -> V.Version -> Pkg.Name -> V.Version -> FilePath
+packageOverride (PackageOverridesCache dir) originalPkgName originalPkgVersion overridingPkgName overridingPkgVersion =
+  dir </> Pkg.toFilePath originalPkgName </> V.toChars originalPkgVersion </> Pkg.toFilePath overridingPkgName </> V.toChars overridingPkgVersion
+
+
 
 -- CACHE