| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
* Writing shell scripts in a Makefile is very error-prone.
* TEST_BUNDLED_GEMS_ALLOW_FAILURES seemed to not work before.
|
|
|
|
|
|
| |
Time#inspect change
* See https://github.com/test-unit/test-unit/issues/165
|
|
|
|
| |
* Otherwise, it takes a very long time to notice those tests broke.
|
|
|
|
| |
https://github.com/ruby/stringio/commit/f0e5027279
|
|
|
|
| |
https://github.com/ruby/stringio/commit/5892663e32
|
|
|
|
| |
https://github.com/ruby/stringio/commit/a37ab7c419
|
|
|
|
| |
https://github.com/ruby/stringio/commit/e8065153b8
|
|
|
|
| |
https://github.com/ruby/stringio/commit/4dfd997e0a
|
|
|
|
| |
https://github.com/ruby/zlib/commit/00ead8cb2c
|
|
|
|
| |
https://github.com/ruby/zlib/commit/8f43b264cd
|
| |
|
|
|
|
| |
[ruby-list:50826]
|
| |
|
| |
|
| |
|
|
|
|
| |
RDoc cannot know if bare words are method name or not.
|
|
|
|
|
|
|
|
|
|
| |
This is due to calling rb_mod_module_eval directly instead of using
rb_funcall_passing_block.
The problem with calling directly is it does not create a new VM
frame, so rb_mod_module_eval was called with no arguments, but with
the keyword given VM frame flag set, which causes problems
internally.
|
|
|
|
|
|
|
| |
If a method accepts no keywords and was called with a keyword, an
ArgumentError was not always issued previously. Force methods that
accept no keywords to go through setup_parameters_complex so that
an ArgumentError is raised if keywords are provided.
|
|
|
|
|
| |
This may be too verbose, if so, maybe it should be moved lower in
the document, or to a separate document.
|
| |
|
|
|
|
|
|
|
| |
* Optimize Array#flatten and flatten! for already flattened arrays
* Add benchmark for Array#flatten and Array#flatten!
[Bug #16119]
|
|
|
|
|
|
|
|
| |
The verbose mode warning has been present for almost 10 years.
If we ever plan to remove these methods, we should make the warning
a regular deprecation warning so that people are aware.
Implements [Feature #15961]
|
|
|
|
|
|
| |
Patch from Matthew Kerwin.
Fixes [Bug #14358]
|
|
|
|
|
|
| |
+ is not a character that requires escaping in Bourne sh.
Fixes [Bug #14429]
|
|
|
|
|
|
|
|
| |
An EPIPE when sending the request should be ignored. Even if you
cannot write more data, you may still be able to read the server's
response.
Fixes [Bug #14466]
|
| |
|
|
|
|
|
| |
Drop catch table entries used in eliminated block, as well as
call_infos. [Bug #16184]
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
a frozen String
* Always the same frozen String for each of these values.
* Avoids extra allocations whenever calling these 3 methods.
* See [Feature #16150]
|
|
|
|
| |
https://github.com/ruby/fileutils/commit/ba3bd6fdfd
|
|
|
|
|
|
| |
Gem::Specification#add_development_dependency.
https://github.com/ruby/fileutils/commit/17a9de6d9b
|
|
|
|
| |
https://github.com/ruby/fileutils/commit/ba81f024cf
|
|
|
|
|
|
|
|
|
|
| |
Previously this would copy the symlink root as a symlink instead
of creating a new root directory. This modifies the source
to expand it using File.realpath before starting the copy.
Fixes Ruby Bug 12123
https://github.com/ruby/fileutils/commit/7359cef359
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
character/block device in /dev
Previously this would give an error such as:
TestFileUtils#test_cp_r_dev [c:/fileutils/test/fileutils/test_fileutils.rb:455]:
[RuntimeError] exception expected, not.
Class: <TypeError>
Message: <"no implicit conversion of nil into String">
https://github.com/ruby/fileutils/commit/0ce0fefbeb
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
frozen object
If FileUtils is included into another object, and verbose mode is
used, a FrozenError is currently raised unless the object has the
@fileutils_output and @fileutils_label instance variables.
This fixes things so that it does not attempt to set the instance
variables, but it still uses them if they are present.
https://github.com/ruby/fileutils/commit/689cb9c56a
|
|
|
|
| |
https://github.com/ruby/fileutils/commit/20bb9ec789
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, this was broken. Trying to copy a FIFO would raise a
NoMethodError if File.mkfifo was defined. Trying to copy a UNIX
socket would raise a RuntimeError as File.mknod is not something
Ruby defines.
Handle the FIFO issue using File.mkfifo instead of mkfifo.
Handle the UNIX Socket issue by creating a unix socket.
Continue to not support character or block devices, raising a
RuntimeError for both.
Add tests for FIFO, UNIX Socket, and character/block devices.
https://github.com/ruby/fileutils/commit/123903532d
|
|
|
|
| |
https://github.com/ruby/fileutils/commit/b701353c53
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes instance_exec and similar methods. It also fixes
Enumerator::Yielder#yield, rb_yield_block, and a couple of cases
with Proc#{<<,>>}.
This support requires the addition of rb_yield_values_kw, similar to
rb_yield_values2, for passing the keyword flag.
Unlike earlier attempts at this, this does not modify the rb_block_call_func
type or add a separate function type. The functions of type
rb_block_call_func are called by Ruby with a separate VM frame, and we can
get the keyword flag information from the VM frame flags, so it doesn't need
to be passed as a function argument.
These changes require the following VM functions accept a keyword flag:
* vm_yield_with_cref
* vm_yield
* vm_yield_with_block
|
| |
|
|
|
|
| |
This commit adds compaction support to `rb_ast_t`.
|
|
|
|
| |
This requires adding rb_proc_call_kw to pass the keyword flag.
|
|
|
|
|
| |
We are calling this in a few other files, it is better to have it
in a header than adding prototypes to the other files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been compiling with:
```
set -lx cflags '-std=c99 -Werror=pedantic -pedantic-errors'
```
But compilation would fail with the following:
```
cont.c:296:90: error: format specifies type 'void *' but the argument has type 'struct fiber_pool_stack *' [-Werror,-Wformat-pedantic]
if (DEBUG) fprintf(stderr, "fiber_pool_stack_alloca(%p): %"PRIuSIZE"/%"PRIuSIZE"\n", stack, offset, stack->available);
~~ ^~~~~
cont.c:467:24: error: format specifies type 'void *' but the argument has type 'struct fiber_pool *' [-Werror,-Wformat-pedantic]
count, fiber_pool, fiber_pool->used, fiber_pool->count, size, fiber_pool->vm_stack_size);
^~~~~~~~~~
cont.c:588:83: error: format specifies type 'void *' but the argument has type 'struct fiber_pool_vacancy *' [-Werror,-Wformat-pedantic]
if (DEBUG) fprintf(stderr, "fiber_pool_stack_acquire: %p used=%"PRIuSIZE"\n", fiber_pool->vacancies, fiber_pool->used);
~~ ^~~~~~~~~~~~~~~~~~~~~
cont.c:736:76: error: format specifies type 'void *' but the argument has type 'rb_fiber_t *' (aka 'struct rb_fiber_struct *')
[-Werror,-Wformat-pedantic]
if (DEBUG) fprintf(stderr, "fiber_stack_release: %p, stack.base=%p\n", fiber, fiber->stack.base);
```
This commit just fixes the pedantic errors
|
| |
|
|
|
|
|
| |
This function is just a synonym for RB_OBJ_WRITTEN, so we can just
directly call that.
|
|
|
|
| |
We don't use this array anymore so we can remove it
|