Load nothing from Tapioca by default #821
Merged
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.
Motivation
The split between top level
tapioca.rb
requires andtapioca/internal.rb
requires was creating an ordering problem. Also, the default require of Tapioca might be pulling into the requiring much more than we intended, and since we do messy things with Sorbet runtime, that could end up being distruptive.Implementation
It is best to not load anything from the default require (we basically define the top-level
Tapioca
namespace and some constants under it, only) and to load everything for the CLI usingtapioca/internal.rb
. This allows us to order the requires so that all the trackers and other runtime patches get loaded before things that depend on them.NOTE: This implies that people who write their own DSL compilers will have to explicitly do a
require "tapioca/dsl/compiler"
.Tests
No new tests.