From: eregontp@... Date: 2020-11-04T10:46:36+00:00 Subject: [ruby-core:100711] [Ruby master Feature#16043] `$LOAD_PATH.resolve_feature_path` should not raise Issue #16043 has been updated by Eregon (Benoit Daloze). Agreed, I added it to the next dev-meeting agenda (#17299) ---------------------------------------- Feature #16043: `$LOAD_PATH.resolve_feature_path` should not raise https://bugs.ruby-lang.org/issues/16043#change-88355 * Author: deivid (David Rodr�guez) * Status: Open * Priority: Normal ---------------------------------------- When I first tried this method, I was expecting it to return `nil` when the given feature is not found. This is because I read in the docs and discussion that this method only searches the feature in the LOAD_PATH, but does not attempt to load it. Raising a load error makes it look that this method tries to load the feature, but I don't think it does that. Also returning `nil` seems friendlier to me because the "feature not found" case is more like an expected outcome of the method than a real error condition, so in most usages this error will actually be rescued for control flow. I attach a patch with the change, and link to the GH PR: https://github.com/ruby/ruby/pull/2317. ---Files-------------------------------- 0001-LOAD_PATH.resolve_feature_path-should-not-raise.patch (1.13 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: