Issue #20971 has been updated by nobu (Nobuyoshi Nakada). Status changed from Open to Assigned Assignee set to matz (Yukihiro Matsumoto) I think it would be OK to remove that warning (and `rb_patch_check` etc totally), if it is recognized officially. @matz What do you think? ---------------------------------------- Feature #20971: Deprecate `rb_path_check` https://bugs.ruby-lang.org/issues/20971#change-111142 * Author: Earlopain (Earlopain _) * Status: Assigned * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- With #16131, various code around $SAFE, taint, etc. has been deprecated and removed. GH PR https://github.com/ruby/ruby/pull/2476. Now, [`rb_path_check`] still exists as part of the public API, with Ruby itself never using or testing it. I believe it should have been deprecated and was simply missed. Should it be deprecated today or is that not worth the effort? Docs for it are pretty vague: https://github.com/ruby/ruby/blob/33f95d632dce42fac35da29eaed33f0a5a4f0dcb/i...
This function is mysterious. What it does is not immediately obvious. Also what it does seems platform dependent.
[`rb_path_check`]: https://github.com/ruby/ruby/blob/33f95d632dce42fac35da29eaed33f0a5a4f0dcb/f... -- https://bugs.ruby-lang.org/