smuggler2 alternatives and similar packages
Based on the "Compiler Plugin" category.
Alternatively, view smuggler2 alternatives based on common mentions on social networks and blogs.
4.7 1.7 smuggler2 VS BinderAnnBinderAnn: Automated Reification of Source Annotations for Monadic EDSLs
Do you think we are missing an alternative of smuggler2 or a related project?
Smuggler2 is a Haskell GHC Source Plugin that automatically
rewrites module imports to produce a minimal set. This may make code easier to read because the provenance of imported names is explcit.
adds or replaces explicit exports to produce a maximalist set for hand pruning. All values, types and classes defined in a module are exported (excluding those that are imported). It does not check whether an exported name is used elsewhere in your package. Limiting exports may make it easier for
ghcto optimise some code.
The Haskell Wiki sets out
the pros and cons of using explicit import lists.
Smuggler2 offers the option
of leaving a module imports open (by not specifiying explcitly what is to be
imported from them) while developing and then getting
Smuggler2 to add minimal
lists of explicit exports. This helps to document modules and, arguably, makes
them easier to read by avoiding the need to qualify names to give an indication
of where they came from. It could also provides a cross-check that only expected
names are being used.
How to use
cabal install --lib smuggler2.
Adding Smuggler2 to your dependencies
smuggler2 to the dependencies of your project and to your compiler flags.
For example, you could include in your project
cabal file something like
flag smuggler2 description: Rewrite sources to cleanup imports, and create explicit exports exports default: False manual: True common smuggler-options if flag(smuggler2) ghc-options: -fplugin=Smuggler2.Plugin build-depends: smuggler2 >= 0.3 && < 0.4
import: smuggler-options in the appropriate
The use of the flag allows you to build with or without source processing. Eg,
$ cabal build -fsmuggler2
using the example above.
You might use this approach to refine your imports or get a starting point for
your exports, but not rewrite them every time you compile. The use of a flag
means that you can also exclude
smuggler2 dependencies from your final builds.
Alternatively, using a local version
If you have installed
smuggler2 from a local copy of this repository, you may
need to add
-package-env default -package smuggler2 to your
you did not install using the
--lib flag to
cabal install. (This will depend
on your setup and your version of
Or use a
The repository also has a very simple
ghc-smuggler2 in the
folder that you can tweak to accomodate your local build environment. This
allows you to run the plugin over your sources without modifying your
$ cabal build -with-compiler=ghc-smuggler2
$ cabal build -w ghc-smuggler2
You can just run
ghcid as usual:
$ ghcid --command='cabal repl'
Smuggler2 has several (case-insensitive) options, which can be set by adding
-fplugin-opt=Smuggler2.Plugin: flags to your
NoImportProcessing- do no import processing
PreserveInstanceImports- remove unused imports, but preserve a library import stub. such as
import Mod (), to import only instances of typeclasses from it. (The default.)
MinimiseImports- remove unused imports, including any that may be needed only to import typeclass instances. This may, therefore, stop the module from compiling.
NoExportProcessing- do no export processing
AddExplicitExports- add an explicit list of all available exports (excluding those that are imported) if there is no existing export list. (The default.) You may want to edit it to keep specific values, types or classes local to the module. At present, a typeclass and its class methods are exported individually. You may want to replace those exports with an abbreviation such as
ReplaceExports- replace any existing module export list with one containing all available exports (which, again, you can, of course, then prune to your requirements).
MakeOpenImportstake a comma-separated list of module names. The specified modules are to be left open if they were open in the sourcee (in the case of
LeaveOpenImports) and made open even if they were not originally (in the case of
MakeOpenImports). For example, you could add
This may be helpful if you use ghc's
NoImplicitPrelude language feature and
import a prelude manually.
PreserveInstanceImports option was sepecified, the
MakeOpenImports options override it for the specified modules, They have
no effect, if
NoImportProcessing was specified. If a module is specified
both to be left open and made open, it will be made open.
- Any other option value is used to generate a source file with a new extension
of the option value (
newin the following example) rather than replacing the original file.
ghc-options: -fplugin=Smuggler2.Plugin -fplugin-opt=Smuggler2.Plugin:new
This will create output files with a
.new suffix rather the overwriting the
Smuggler2rewrites the existing imports, rather than attempting to prune them. (This is a more aggressive approach than
smugglerwhich focuses on removing redundant imports.) It has advantages and disadvantages. The advantage is that a minimal set of imports is generated in a reproducable format. So you can just import a library without specifying any specific imports and
Smuggler2will add an explict list of things that are used from it. This can be a useful check and better document your modules. The disdvantage is that imports may be reordered, comments and blank lines dropped, external imports mixed with external, etc.
Smuggler2does not remove imports completely because an import may be being used to only import instances of typeclasses, So it will leave stubs like
import Mod ()
that you may want to remove manually. Alternatively use the
option to remove them anyway, at the risk of producing code that fails to
CPP files will not be processed correctly: the imports will be generated for current CPP settings and any CPP annotations in the import block will be discarded. This may be a particular problem if you are writing code for several generations of
basefor example. Nevetheless,
Smuggler2will generate a new CPP preprocessed output file with a
-cppsuffix. retrie solves this problem generating all possible versions of the module (exponential in the number of
#ifdirectives), operating on each version individually, and splicing results back into the original file. A tour de force!
ghcdon't have full support for distinguishing dependent packages from plug-ins you will probably want to ensure that the build the dependencies for your project that are installed into your local package db first, before enabling
ghc-smuggler2otherwise they will all be processed by it too, as your project builds, which should do no harm, but will increase your build time:
$ cabal build --dependencies-only $ cabal clean $ cabal -w ghc-smuggler2
if you import patterns synonyms from a library without naming them explicitly in an import list, you do not need the
PatternSynonymslanguage extension. If you import them explicitly, using the
patternkeyword, the language extension is required (otherwise you will just get a syntax error on compilation).
Smuggler2.Pluginwill not add that for you.
Multiple separate import lines referring to the same library are not consolidated
.lhsfiles will processed into ordinary haskell files wth a
hidingimports are not needed and replaced by explicit ones.
Smuggler2 is robust -- it can chew through the
Agda codebase of over 370 modules with complex
interdependencies and be tripped over by only
a couple of ambiguous exports (are we trying to export something defined in the current module or something with the same name from an imported module)
and a couple of imports where both qualifed and unqualifed version of the module are imported and there are references to both qualified and unqualifed version of the same names
smuggler2depends on the current
baselibrary to check whether an import is redundant. Different versions of the compiler may, of course, need different slightly imports, typically from
base. The base library changelog provides some details of what was made available when.
The plugin does not seem to run reliably on Windows. This is probably more of an issue with the way that the tests are run, than
cabaldoes not have a particular way of specifying plugins. (See, eg, https://gitlab.haskell.org/ghc/ghc/issues/11244 and https://github.com/haskell/cabal/issues/2965) which would allow cleaner separation of user code and plugin-code
Smuggler2will not compile with earlier versions.
- The test golden values are for
ghc-8.8.3. Some of them fail on
ghc-8.6.5because it seems to need to import
Data.Boolwhereas later versions of GHC don't. The results compile on
ghc-8.6.5and later anyway, but the imports are not as minimal for later versions as they could be.
ghc-exactprint 0.6.3.1adds extra '\r` inside comments under Windows, so the tests fail.
cabal >= 3.0(ideally
- The Windows version of the plugin is a bit flaky because of apparent compiler bugs.
How to build
There is a
Makefile at the root of the distribution that covers various
maintenance tasks, including building the package.
$ cabal update $ cabal build --write-ghc-environment-files=always
Writing the ghc environment file allows tests to be run from within the
ghc -fplugin=Smuggler2.Plugin without needing to use
cabal exec -- ghc -fplugin=Smugler2.Plugin or a
-package smuggler2 flag.
cabal clean to get rid of it, to avoid surprises when you are done.
To build with debugging:
$ cabal build -fdebug --write-ghc-environment-files=always
Curently this just adds an
-fdump-minimal-imports parameter to GHC
How to run tests
There is a
tasty-golden-based test suite that can be run by
$ cabal test smuggler2-test --enable-tests
Further help can be found by
$ cabal run smuggler2-test -- --help
(note the extra
For example, if you are running on
ghc-8.6.5 you can
$ cabal run smuggler2-test -- --accept
to update the golden outputs to the current results of (failing) tests.
It is sometimes necessary to run
cabal clean before running tests to ensure
that old build artefacts do not lead to misleading results.
Importing a test module from another test module in the same directory is likely
to lead to race conditions as 'Tasty' runs tests in parallel and so will try to
generate the same
smuggler2 output both when the imported module is being
tested directly and when it is being processed when the importing module is
being tested. Put the imported module in a subdirectory to avoid this issue, as
the test harness only looks for tests in
test\tests and not its
smuggler2 uses the
library to modiify the
source code. The documentation for the library is fairly spartan, and the
library is not widely used, at least in publicly available code, so the use here
can, no doubt, be optimised.
The library is needed because the annotated AST that GHC generates does not have
enough information to reconstitute the original source. Some parts of the
renamed syntax tree (for example, imports) are not found in the typechecked one.
ghc-exactprint provides parsers that preserve this information, which is
stored in a separate
Map used to generate properly formatted source
To make manipulation of GHC's AST and
ghc-exactprint provides a set of Transform functions. These are intended to
facilitate making changes to the AST and adjusting the
Anns to suit the
These functions are said to be under heavy development. It is not entirely obvious how they are intended to be used or composed. The approach provided by
retriewraps an AST and
Annsinto a single type that seems to make AST transformations easier to compose and reduces the risk of the
Annsand AST getting out of sync as it is being transformed, something with which the type system doesn't help you since the
Annsare stored as a
smuggler2 uses GHC to generate a set of minimal imports. It
- parses the original file
- dumps the minimal exports that GHC generates and parses them back in (to pick up the annotations needed for printing)
- drops implicit imports (such as Prelude) and, optionally, imports that are for instances only
- replaces the original imports with minimal ones
exactPrints the result back over the original file (or one with a different suffix, if that was specified as option to
This round tripping is needed because the AST that
ghc provides does not have
enough information in it to reconstitute the source (which is why
Exports are simpler to deal with as GHC's
exports_from_avail does the work.
- Smuggler2 was is a rewrite of
retriea code modding tool that works with GHC 8.10.1
refact-global-hsean ambitious import refactoring tool. This uses
ghc-exactprintand so may not work with current versions of GHC.
- These blog posts contain some fragments on the topic of using
ghc-exactprintto manipulate import lists Terser import declarations and GHC API (The site doesn't always seem to be up.)
*Note that all licence references and agreements mentioned in the smuggler2 README section above are relevant to that project's source code only.