| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
This issue is related to #3640.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We know this is not perfect, but this change makes hack like #3679
bit harder. Harmless for useful cases.
|
|
|
|
The patch deallocate the memory in `mrb_default_allocf` but that
hinders GC in `mrb_realloc`.
|
|
|
|
|
|
Top-level local variables contained junk after ab25eaea2
|
|
|
|
|
|
The old order generated some strings with their class set to NULL.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Redundant `mark_context() is far better than crashes.
|
|
|
|
This reverts commit e26e11860466676e5713fa0d9ab268ea8dbdcef9.
Fix #3664
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|