Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix typos [ci skip] | Kazuhiro NISHIYAMA | 2020-09-06 | 1 | -3/+3 |
| | |||||
* | Fixed heap-use-after-free on racter | Nobuyoshi Nakada | 2020-09-04 | 1 | -0/+8 |
| | |||||
* | check multi_ractor mode at main_p | Koichi Sasada | 2020-09-04 | 1 | -3/+7 |
| | | | | | | | | | rb_ractor_main_p() need to access to the ractor pointer in TLS. However it is slow operation so that we need to skip this check if it is not multi-ractor mode (!ruby_multi_ractor). This performance regression is pointed at https://bugs.ruby-lang.org/issues/17100#note-27 | ||||
* | Initialize loop variables of list_for_each for MS VC | Nobuyoshi Nakada | 2020-09-04 | 1 | -3/+3 |
| | |||||
* | Introduce Ractor mechanism for parallel execution | Koichi Sasada | 2020-09-03 | 1 | -0/+1877 |
This commit introduces Ractor mechanism to run Ruby program in parallel. See doc/ractor.md for more details about Ractor. See ticket [Feature #17100] to see the implementation details and discussions. [Feature #17100] This commit does not complete the implementation. You can find many bugs on using Ractor. Also the specification will be changed so that this feature is experimental. You will see a warning when you make the first Ractor with `Ractor.new`. I hope this feature can help programmers from thread-safety issues. |