Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Improve writing.

  • Loading branch information...
commit d71337fc5a9b069f377119e0ccda7b682562df87 1 parent 1a109f3
@marcotmarcot authored
Showing with 1 addition and 1 deletion.
  1. +1 −1  marcot.tex
View
2  marcot.tex
@@ -332,7 +332,7 @@ \section{Modules}
\section{Contributions of this dissertation}
-However, the simplicity of the module system is partly hindered by the special treatment given to the scope of instances, for which there are not control on exportation and importation.
+However, the simplicity of the module system is partly hindered by the special treatment given to the scope of instances, for which there is no control on exportation and importation.
As defined in the Modules chapter of the Haskell 2010 Report \citep[section~5.4]{report}, a type class ``instance declaration is in scope if and only if a chain of \texttt{import} declarations leads to the module containing the instance declaration''.
Because of this, it is not possible for a module to import two modules that defines the same instance, that is, an instance of the same type class to the same data type, if the importing module, or any module that imports it, use the instance. This happens if the both if the definitions are different or the same on the different modules. This is a
Please sign in to comment.
Something went wrong with that request. Please try again.