Sample
Demonstrate that calling Zeitwerk::Loader.setup twice does NOT raise an error
sha256:a5bd61b88ee5503ac32ff50c101ec7c975cdb0b65042a507ecefa5c3fae19bf2
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Demonstrate that calling Zeitwerk::Loader.setup twice does NOT raise an error HOW
- Packages
- zeitwerk 2.8.3
- Environment
- ruby
- Created
- 2026-08-17T02:50:07Z
Commonly assumed
Calling Zeitwerk::Loader.setup multiple times on the same loader raises a Zeitwerk::Error
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Second call to loader.setup does NOT raise an error
Files
- Gemfile
- Gemfile.lock
- csx.json
- lib/dummy.rb
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9