Rename haskell_import to haskell_toolchain_library #843
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a substantial breaking change. But a simple one to handle: it
can be done with
everywhere. I considered marking this as deprecated instead, but that
won't help much: the deprecation spam will make things unbearable
without switching to the new name anyways.
The motivation for this change can be found in #440 and #838.
haskell_import
was always poorly named, because it did notcorrespond to precedent in the CC and Java rules. Whereas those rules
"import" concrete artifacts with some metadata into the dependency
graph, our old
haskell_import
was merely giving a name in thedependency graph to stuff that is magically available from somewhere,
namely the GHC boot libraries.
I will be submitting a followup PR to implement a new
haskell_import
that is similar in spirit to
cc_import
andjava_import
, onceI manage to solve/workaround the two following bugs:
Meanwhile this PR just prepares the ground, by moving the existing
haskell_import
out of the way and renaming it tohaskell_toolchain_library
.