| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Even though the returning value is retrieved from the stack,
it may be freed if GC is caused during stack rewinding
(e.g. ensure calls).
|
|
|
|
They didn't work well with inexact numbers (inf,nan). Fix #3671
|
|
Fix #3668
|
|
|
|
|
|
|
|
|
|
Related to #3662
|
|
When MRB_INT64, valid value range of mrb_int is bigger than double,
which only has 53 bits significant precision.
|
|
|
|
|
|
|
|
|
|
Without this cast, `long int:63` can cause warnings.
|
|
|
|
Redundant `mark_context() is far better than crashes.
|
|
The fix was proposed by @block8437. Thank you.
|
|
|
|
This reverts commit e26e11860466676e5713fa0d9ab268ea8dbdcef9.
Fix #3664
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead of preserving a backtrace in `mrb_state`, `mrb_exc_set`
keeps packed backtrace in an exception object. `#backtrace` unpacks
it to an array of strings.
|
|
|
|
|
|
|
|
|
|
|
|
Should raise SyscallError on IO#syswrite
|
|
Fix some spec for IO#sysread
|
|
|
|
|
|
|
|
String#concat: Try to convert when not string
|
|
instead of IOError
|
|
|
|
|
|
Avoid call to_s during backtrace traversal
|
|
|