opal/opal

An inconsistency with requiring in MRI vs. Opal

Open

#778 opened on 2015年3月26日

GitHub で見る
 (7 comments) (0 reactions) (0 assignees)Ruby (4,766 stars) (382 forks)batch import
help wantedv1.3

説明

So, I was recently having some problems with require in Opal. In MRI, requiring files works like so: main.rb

require "./file1.rb"
require "./file2.rb"

file1.rb

puts "file1"

file2.rb

puts "file2"

If you run the above code, you'll get file1 and file2 printed out. Also note that if you remove the ./ from the require statements, the above code will not work. But, in Opal (as of 0.7.1), using the ./ syntax does not work and requiring only works without using ./. In Opal 0.6.x, it seems to be that you can require with either ./ or without it. As far as I can tell, this problem seems to be an inconsistency between MRI and Opal.

コントリビューターガイド

技術スタック
rubyjavascript
領域
backendtooling
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Ruby require semanticsOpal basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
The issue describes a difference in require behavior between MRI and Opal. Investigate Opal's require implementation in the source code (likely in lib/opal/ or compiler files). Compare how Opal 0.6.x handled relative paths vs 0.7.1. Look for changes in the require resolution logic that may have introduced the inconsistency.