brew/Library/Homebrew/load_path.rb

# typed: true
# frozen_string_literal: true

require "pathname"

HOMEBREW_LIBRARY_PATH = Pathname(__dir__).realpath.freeze

$LOAD_PATH.push HOMEBREW_LIBRARY_PATH.to_s

require "vendor/bundle/bundler/setup"
require "homebrew_bootsnap"

unless defined?(Bootsnap)
  $LOAD_PATH.select! { |d| Pathname(d).directory? }
  $LOAD_PATH.uniq!
end
Move type annotations into files. 2020-10-10 14:16:11 +02:00			`# typed: true`
Add frozen_string_literal to all files. 2019-04-19 15:38:03 +09:00			`# frozen_string_literal: true`

Add `$LOAD_PATH` for RuboCop cops. 2018-09-02 23:30:07 +02:00			`require "pathname"`

Fix mutable constants violations. 2019-04-19 21:46:20 +09:00			`HOMEBREW_LIBRARY_PATH = Pathname(__dir__).realpath.freeze`
Add `$LOAD_PATH` for RuboCop cops. 2018-09-02 23:30:07 +02:00
load_path: trim entries where possible to fix Ruby crashes 2020-04-01 10:23:18 +01:00			`$LOAD_PATH.push HOMEBREW_LIBRARY_PATH.to_s`
Use Bundler to manage vendor directory Rather than having to manually keep track of what version each thing in here is and copy files around by hand on update let's use Bundler's standalone mode and careful use of `.gitignore` to help us do it. This means a `bundle update --standalone` will allow us to update all gems in vendor. We could consider vendoring other gems this way in future but I'd suggest only doing this for gems with no dependencies or at least gems with no native extensions. The only gem this applies to that we currently use is `ruby-prof` and I'm not convinced it's widely used enough to warrant vendoring for everyone. Perhaps that's another criteria: it should be functionality that's used by non-developer commands and/or normal Homebrew usage. 2018-09-13 15:24:18 +01:00
Move all gems to vendor/bundle, remove vendor/bundle-standlone. 2019-02-21 15:41:42 +00:00			`require "vendor/bundle/bundler/setup"`
homebrew_bootsnap: various improvements. - Add `HOMEBREW_NO_BOOTSNAP` as well as `HOMEBREW_BOOTSNAP` - Guard the whole file rather than `raise` on inclusion. - Use `HOMEBREW_CACHE` instead of `HOMEBREW_TEMP` - Don't try to use Bootsnap with macOS portable ruby 2021-02-02 11:50:44 +00:00			`require "homebrew_bootsnap"`
load_path: trim entries where possible to fix Ruby crashes 2020-04-01 10:23:18 +01:00
homebrew_bootsnap: various improvements. - Add `HOMEBREW_NO_BOOTSNAP` as well as `HOMEBREW_BOOTSNAP` - Guard the whole file rather than `raise` on inclusion. - Use `HOMEBREW_CACHE` instead of `HOMEBREW_TEMP` - Don't try to use Bootsnap with macOS portable ruby 2021-02-02 11:50:44 +00:00			`unless defined?(Bootsnap)`
Add HOMEBREW_BOOTSNAP to optionally use Bootsnap > Bootsnap is a library that plugs into Ruby, with optional support > for ActiveSupport and YAML, to optimize and cache expensive > computations. https://github.com/Shopify/bootsnap For our case that translates to "repeated calls to `brew` have reductions in the time spend `require`ing speeding up the process boot time". For example: ``` $ hyperfine --warmup=2 "unset HOMEBREW_BOOTSNAP; brew info wget" "export HOMEBREW_BOOTSNAP=1; brew info wget" Benchmark #1: unset HOMEBREW_BOOTSNAP; brew info wget Time (mean ± σ): 2.417 s ± 0.032 s [User: 659.0 ms, System: 855.5 ms] Range (min … max): 2.382 s … 2.464 s 10 runs Benchmark #2: export HOMEBREW_BOOTSNAP=1; brew info wget Time (mean ± σ): 1.862 s ± 0.064 s [User: 425.3 ms, System: 566.8 ms] Range (min … max): 1.736 s … 1.952 s 10 runs Summary 'export HOMEBREW_BOOTSNAP=1; brew info wget' ran 1.30 ± 0.05 times faster than 'unset HOMEBREW_BOOTSNAP; brew info wget' ``` 2021-01-21 12:34:04 +00:00			`$LOAD_PATH.select! { \|d\| Pathname(d).directory? }`
			`$LOAD_PATH.uniq!`
			`end`