Ruby allows to load files using Kernel.load without explicitly specifying the relative path with . I'm not sure it's a bug or a feature, but since documentation in master doesn't say anything about it and the behavior differs from require where it was changed intentionally, I consider it a bug
I don’t this is an implementation bug, but a documentation issue.
Shouldn't behavior be consistent with require, though?
I don't think so. load has always been able to load files that exist relative to the current directory, and require has not. Technically, in Ruby <1.9, require worked similarly because '.' was in the default load path). load and require are different in many other ways, and changing this to increase the consistency between them doesn't make sense to me.
Changing load's behavior would definitely break things. I agree with @nobu (Nobuyoshi Nakada) that this is a documentation issue, and I'll try to update the documentation to explain it.
Document that Kernel#load will load relative to current directory [ci skip]
Update and format the Kernel#load documentation to separate the
three cases (absolute path, explicit relative path, other), and
also document that it raises LoadError on failure.
Updated by 
Updated by 
Updated by 
Updated by jeremyevans (Jeremy Evans)