mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
![]() This makes: ```ruby args = [1, 2, -> {}]; foo(*args, &args.pop) ``` call `foo` with 1, 2, and the lambda, in addition to passing the lambda as a block. This is different from the previous behavior, which passed the lambda as a block but not as a regular argument, which goes against the expected left-to-right evaluation order. This is how Ruby already compiled arguments if using leading arguments, trailing arguments, or keywords in the same call. This works by disabling the optimization that skipped duplicating the array during the splat (splatarray instruction argument switches from false to true). In the above example, the splat call duplicates the array. I've tested and cases where a local variable or symbol are used do not duplicate the array, so I don't expect this to decrease the performance of most Ruby programs. However, programs such as: ```ruby foo(*args, &bar) ``` could see a decrease in performance, if `bar` is a method call and not a local variable. This is not a perfect solution, there are ways to get around this: ```ruby args = Struct.new(:a).new([:x, :y]) def args.to_a; a; end def args.to_proc; a.pop; ->{}; end foo(*args, &args) # calls foo with 1 argument (:x) # not 2 arguments (:x and :y) ``` A perfect solution would require completely disabling the optimization. Fixes [Bug #16504] Fixes [Bug #16500] |
||
---|---|---|
.. | ||
fixtures | ||
predefined | ||
regexp | ||
shared | ||
alias_spec.rb | ||
and_spec.rb | ||
array_spec.rb | ||
BEGIN_spec.rb | ||
block_spec.rb | ||
break_spec.rb | ||
case_spec.rb | ||
class_spec.rb | ||
class_variable_spec.rb | ||
comment_spec.rb | ||
constants_spec.rb | ||
def_spec.rb | ||
defined_spec.rb | ||
delegation_spec.rb | ||
encoding_spec.rb | ||
END_spec.rb | ||
ensure_spec.rb | ||
execution_spec.rb | ||
file_spec.rb | ||
for_spec.rb | ||
hash_spec.rb | ||
heredoc_spec.rb | ||
if_spec.rb | ||
lambda_spec.rb | ||
line_spec.rb | ||
loop_spec.rb | ||
magic_comment_spec.rb | ||
match_spec.rb | ||
metaclass_spec.rb | ||
method_spec.rb | ||
module_spec.rb | ||
next_spec.rb | ||
not_spec.rb | ||
numbered_parameters_spec.rb | ||
numbers_spec.rb | ||
optional_assignments_spec.rb | ||
or_spec.rb | ||
order_spec.rb | ||
pattern_matching_spec.rb | ||
precedence_spec.rb | ||
predefined_spec.rb | ||
private_spec.rb | ||
proc_spec.rb | ||
range_spec.rb | ||
README | ||
redo_spec.rb | ||
regexp_spec.rb | ||
rescue_spec.rb | ||
retry_spec.rb | ||
return_spec.rb | ||
safe_navigator_spec.rb | ||
safe_spec.rb | ||
send_spec.rb | ||
singleton_class_spec.rb | ||
source_encoding_spec.rb | ||
string_spec.rb | ||
super_spec.rb | ||
symbol_spec.rb | ||
throw_spec.rb | ||
undef_spec.rb | ||
unless_spec.rb | ||
until_spec.rb | ||
variables_spec.rb | ||
while_spec.rb | ||
yield_spec.rb |
There are numerous possible way of categorizing the entities and concepts that make up a programming language. Ruby has a fairly large number of reserved words. These words significantly describe major elements of the language, including flow control constructs like 'for' and 'while', conditional execution like 'if' and 'unless', exceptional execution control like 'rescue', etc. There are also literals for the basic "types" like String, Regexp, Array and Fixnum. Behavioral specifications describe the behavior of concrete entities. Rather than using concepts of computation to organize these spec files, we use entities of the Ruby language. Consider looking at any syntactic element of a Ruby program. With (almost) no ambiguity, one can identify it as a literal, reserved word, variable, etc. There is a spec file that corresponds to each literal construct and most reserved words, with the exceptions noted below. There are also several files that are more difficult to classify: all predefined variables, constants, and objects (predefined_spec.rb), the precedence of all operators (precedence_spec.rb), the behavior of assignment to variables (variables_spec.rb), the behavior of subprocess execution (execution_spec.rb), the behavior of the raise method as it impacts the execution of a Ruby program (raise_spec.rb), and the block entities like 'begin', 'do', ' { ... }' (block_spec.rb). Several reserved words and other entities are combined with the primary reserved word or entity to which they are related: false, true, nil, self predefined_spec.rb in for_spec.rb then, elsif if_spec.rb when case_spec.rb catch throw_spec.rb