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.
Fixes #2636
Alternative to #2646 (which is this PR but for one call)
Reading the original code's comment:
The purpose of this function is to not elide an import if it had been touched by a custom before transformer.
In Strada, this was fine. The ts transformer went first and did everything under the sun; import elision, type removal, etc.
But now, we split things up. The type eraser runs before the import elider, and the eraser can touch imports (and even elide them itself). This puts us directly in the path of
isElisionBlocked.We don't have before transformers, and it's nontrivial to attempt to mush these transformers back together again.
I think it's probably okay to just delete
isElisionBlockedand address this later if we find it to be a problem.Funnily, if you delete
isElisionBlockedfrom Strada, nothing breaks!